[Kernel-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle

[Andrea Righi]

Interesting that the d3cold_allowed change made some differences (I'm
assuming it was failing 100% of the times before that change).

Few more questions. After a bad resume:

1) are there unkillable processes (D state) in the system (`ps axuw |
grep D`)?

2) does `sudo iwlist wlp4s0 scan` return any error or does it hang
indefinitely?

3) do you have bluetooth enabled (what's the output of `sudo rfkill
list`)?

As a temporary workaround you can automate the modprobe trick (#3) doing
something like the following:

$ cat /lib/systemd/system-sleep/iwlmvm.sh
#!/bin/sh
case $1 in
pre)
modprobe -r iwlmvm
;;
post)
modprobe iwlmvm
;;
esac

But it'd be nice to find a proper solution to this. Thanks!

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

Title:
  Wifi not working after suspend/resume cycle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  About 75% of the time for the past few weeks (I don't have a time
  where this started), my wifi is not working after resume from suspend.
  I'm happy to provide more debugging info if needed.

  I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just
  to see after the resume, and didn't re-enable the card.

  The symptoms are, the wlp4so interface is DOWN, I can't bring it up.
  gnome-network-manager widget turning the interface off/on doesn't
  work.  I don't see anything glaring in dmesg.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-generic 5.0.0.14.15
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpb4587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  7 18:49:01 2019
  InstallationDate: Installed on 2018-06-18 (323 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic 
root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-14-generic N/A
   linux-backports-modules-5.0.0-14-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET52W(1.37)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

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

[bugproxy]

--- Comment From vipar...@in.ibm.com 2019-05-09 02:51 EDT---
(In reply to comment #25)
> upgraded the firmware on dradis to P9DSU20190404_IBM_prod_sign.pnor and
> tested with bionic and disco and the issue does not reproduce. Marking this
> bug as fix-committed, and if you are able to reproduce this again please
> re-open this bug.

As i understand that fix is in firmware and no fix dropped into Linux
(bionic/disco) And thus this bug should be rejected as "not a bug" from Linux 
point
of view as no linux fix is dropped here ?  Please advise.

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

Title:
  CPU hard lockup when turning CPU back online on Bionic P9

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Found on another Boston Power9 box "dradis".

  Steps to reproduce:
  1. Check online CPUs
   $ cat /sys/devices/system/cpu/online 
   0-159
  2. Do a CPU hotplug to take one off:
   $ echo 0 | sudo tee /sys/devices/system/cpu/cpu159/online 
   0
  3. Check dmesg, you should see:
   [  410.890106] IRQ 174: no longer affine to CPU159
  4. Put that CPU back online and check dmesg again:
   $ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online

  System complains about CPU hard lockup:
  [  410.890106] IRQ 174: no longer affine to CPU159
  [  421.168052] Watchdog CPU:128 Hard LOCKUP
  [  421.168054] Modules linked in: joydev input_leds mac_hid idt_89hpesx 
ipmi_powernv opal_prd ipmi_devintf ibmpowernv ofpart at24 cmdlinepart 
uio_pdrv_genirq uio powernv_flash mtd ipmi_msghandler vmx_crypto sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas uas 
usb_storage ast hid_generic i2c_algo_bit ttm drm_kms_helper usbhid syscopyarea 
sysfillrect sysimgblt hid fb_sys_fops crct10dif_vpmsum crc32c_vpmsum drm i40e 
aacraid
  [  421.168108] CPU: 128 PID: 778 Comm: watchdog/128 Not tainted 
4.15.0-48-generic #51-Ubuntu
  [  421.168109] NIP:  c0d082e8 LR: c016c3b0 CTR: 
c0ac5d80
  [  421.168111] REGS: c0003f9ffd80 TRAP: 0900   Not tainted  
(4.15.0-48-generic)
  [  421.168112] MSR:  90009033   CR: 24000484 
 XER: 
  [  421.168118] CFAR: c016c3ac SOFTE: 0 
 GPR00: c016c3b0 c000200e55743af0 c16eb400 
c000200e614a8f20 
 GPR04: 088c c000200e614a4360 c000fd6879b8 
0008 
 GPR08: 0054cd92 389fd980 8080 
0005 
 GPR12: c0ac5d80 cfad8000 c013e648 
c00ff90e9640 
 GPR16:    
 
 GPR20:   c000200e55852b80 
200e602d 
 GPR24: c000200e614a8580  c0d01ff0 
c000200e614a6fb8 
 GPR28: c000200e614a8880 088c c000200e614a8580 
c000200e614a8f20 
  [  421.168142] NIP [c0d082e8] _raw_spin_lock+0x28/0xe0
  [  421.168146] LR [c016c3b0] update_curr_rt+0x1d0/0x3f0
  [  421.168147] Call Trace:
  [  421.168150] [c000200e55743af0] [c171dd78] 
__per_cpu_offset+0x0/0x4000 (unreliable)
  [  421.168154] [c000200e55743b20] [c016c2b0] update_curr_rt+0xd0/0x3f0
  [  421.168156] [c000200e55743bb0] [c016c7bc] dequeue_task_rt+0x3c/0xf0
  [  421.168159] [c000200e55743bf0] [c014e9b0] 
deactivate_task+0xb0/0x160
  [  421.168161] [c000200e55743c70] [c0d0187c] __schedule+0x3bc/0xaf0
  [  421.168164] [c000200e55743d40] [c0d01ff0] schedule+0x40/0xc0
  [  421.168167] [c000200e55743d60] [c0144bd4] 
smpboot_thread_fn+0x284/0x290
  [  421.168169] [c000200e55743dc0] [c013e7e8] kthread+0x1a8/0x1b0
  [  421.168172] [c000200e55743e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
  [  421.168173] Instruction dump:
  [  421.168175] 7c0803a6 4b98 3c4c009e 38423140 7c0802a6 6000 fbe1fff8 
f821ffd1 
  [  421.168179] 7c7f1b78 3940 994d028d 814d0008 <7d201829> 2c09 
40c20010 7d40192d 

  But the CPU is actually back online:
  $ cat /sys/devices/system/cpu/online 
  0-159
  $ cat /sys/devices/system/cpu/cpu159/online 
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  2 08:06 seq
   crw-rw 1 root audio 116, 33 May  2 08:06 timer
  AplayDevices: Error: [Errno

[Kernel-packages] [Bug 1828350] [NEW] Add support for Intel I210 NIC

[Juerg Haefliger]

Private bug reported:

== SRU Justification ==

The Precise 3.2 kernel doesn't support the Intel I210 NIC. It's a fairly
old and common NIC which is also in my test system. It would help with
testing Precise if that NIC was supported.

== Fix ==

Backport the following 3 commits wich add I210 support:
  - igb: Fix incorrect RAR address entries for i210/i211 device.
  - igb: Add Support for new i210/i211 devices.
  - igb: Add function and pointers for 82580 low power state settings.

== Regression Potential ==

Low. This is mostly new code that is only exercised when an I210 NIC is
present. There is some shuffling around and the introduction of low
power settings handling for other NIC types as well so there is some
risk. But it's isolated to the igb NIC driver.

== Test Case ==

Boot a patched kernel and verify the NIC is recognized and the network
comes up.

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

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

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

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

** Information type changed from Public to Private

** Information type changed from Private to Private Security

** Information type changed from Private Security to Private

** Information type changed from Private to Public

** Information type changed from Public to Private

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

Title:
  Add support for Intel I210 NIC

Status in linux package in Ubuntu:
  New
Status in linux source package in Precise:
  Confirmed

Bug description:
  == SRU Justification ==

  The Precise 3.2 kernel doesn't support the Intel I210 NIC. It's a
  fairly old and common NIC which is also in my test system. It would
  help with testing Precise if that NIC was supported.

  == Fix ==

  Backport the following 3 commits wich add I210 support:
- igb: Fix incorrect RAR address entries for i210/i211 device.
- igb: Add Support for new i210/i211 devices.
- igb: Add function and pointers for 82580 low power state settings.

  == Regression Potential ==

  Low. This is mostly new code that is only exercised when an I210 NIC
  is present. There is some shuffling around and the introduction of low
  power settings handling for other NIC types as well so there is some
  risk. But it's isolated to the igb NIC driver.

  == Test Case ==

  Boot a patched kernel and verify the NIC is recognized and the network
  comes up.

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

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

[Kernel-packages] [Bug 1827343] Re: CPU hard lockup when turning CPU back online on Bionic P9

[Andrew Cloke]

Po-Hsu Lin (cypressyew) are you able to verify that the firmware update
has indeed resolved 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/1827343

Title:
  CPU hard lockup when turning CPU back online on Bionic P9

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Found on another Boston Power9 box "dradis".

  Steps to reproduce:
  1. Check online CPUs
   $ cat /sys/devices/system/cpu/online 
   0-159
  2. Do a CPU hotplug to take one off:
   $ echo 0 | sudo tee /sys/devices/system/cpu/cpu159/online 
   0
  3. Check dmesg, you should see:
   [  410.890106] IRQ 174: no longer affine to CPU159
  4. Put that CPU back online and check dmesg again:
   $ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online

  System complains about CPU hard lockup:
  [  410.890106] IRQ 174: no longer affine to CPU159
  [  421.168052] Watchdog CPU:128 Hard LOCKUP
  [  421.168054] Modules linked in: joydev input_leds mac_hid idt_89hpesx 
ipmi_powernv opal_prd ipmi_devintf ibmpowernv ofpart at24 cmdlinepart 
uio_pdrv_genirq uio powernv_flash mtd ipmi_msghandler vmx_crypto sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas uas 
usb_storage ast hid_generic i2c_algo_bit ttm drm_kms_helper usbhid syscopyarea 
sysfillrect sysimgblt hid fb_sys_fops crct10dif_vpmsum crc32c_vpmsum drm i40e 
aacraid
  [  421.168108] CPU: 128 PID: 778 Comm: watchdog/128 Not tainted 
4.15.0-48-generic #51-Ubuntu
  [  421.168109] NIP:  c0d082e8 LR: c016c3b0 CTR: 
c0ac5d80
  [  421.168111] REGS: c0003f9ffd80 TRAP: 0900   Not tainted  
(4.15.0-48-generic)
  [  421.168112] MSR:  90009033   CR: 24000484 
 XER: 
  [  421.168118] CFAR: c016c3ac SOFTE: 0 
 GPR00: c016c3b0 c000200e55743af0 c16eb400 
c000200e614a8f20 
 GPR04: 088c c000200e614a4360 c000fd6879b8 
0008 
 GPR08: 0054cd92 389fd980 8080 
0005 
 GPR12: c0ac5d80 cfad8000 c013e648 
c00ff90e9640 
 GPR16:    
 
 GPR20:   c000200e55852b80 
200e602d 
 GPR24: c000200e614a8580  c0d01ff0 
c000200e614a6fb8 
 GPR28: c000200e614a8880 088c c000200e614a8580 
c000200e614a8f20 
  [  421.168142] NIP [c0d082e8] _raw_spin_lock+0x28/0xe0
  [  421.168146] LR [c016c3b0] update_curr_rt+0x1d0/0x3f0
  [  421.168147] Call Trace:
  [  421.168150] [c000200e55743af0] [c171dd78] 
__per_cpu_offset+0x0/0x4000 (unreliable)
  [  421.168154] [c000200e55743b20] [c016c2b0] update_curr_rt+0xd0/0x3f0
  [  421.168156] [c000200e55743bb0] [c016c7bc] dequeue_task_rt+0x3c/0xf0
  [  421.168159] [c000200e55743bf0] [c014e9b0] 
deactivate_task+0xb0/0x160
  [  421.168161] [c000200e55743c70] [c0d0187c] __schedule+0x3bc/0xaf0
  [  421.168164] [c000200e55743d40] [c0d01ff0] schedule+0x40/0xc0
  [  421.168167] [c000200e55743d60] [c0144bd4] 
smpboot_thread_fn+0x284/0x290
  [  421.168169] [c000200e55743dc0] [c013e7e8] kthread+0x1a8/0x1b0
  [  421.168172] [c000200e55743e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
  [  421.168173] Instruction dump:
  [  421.168175] 7c0803a6 4b98 3c4c009e 38423140 7c0802a6 6000 fbe1fff8 
f821ffd1 
  [  421.168179] 7c7f1b78 3940 994d028d 814d0008 <7d201829> 2c09 
40c20010 7d40192d 

  But the CPU is actually back online:
  $ cat /sys/devices/system/cpu/online 
  0-159
  $ cat /sys/devices/system/cpu/cpu159/online 
  1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  2 08:06 seq
   crw-rw 1 root audio 116, 33 May  2 08:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  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:
  Date: Thu May  2 08:16:36 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  PciMultimedia:
   
  ProcFB: 0 astdr

[Kernel-packages] [Bug 1828351] [NEW] RAID 10 with MegaRaid controller gives poor write performance

[Nicolas Pochet]

Public bug reported:

On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
A simple test:
dd if=/dev/zero of=out bs=1M count=100
Outputs a 35MB/s speed.

The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
Strip size: 64K
Access Policy: RW
Read Policy: Normal
Write Policy: Writethrough
IO Policy: Direct
Disable BGI: No

uname -a
4.15.0-48-generic #51-Ubuntu SMP

[0]
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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


** Tags: 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/1828351

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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

[Kernel-packages] [Bug 1828026] [NEW] gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Failed on Moonshot nodes.


FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

# TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 
-machine gic-version=2 -append 'mmio'
timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.6k28Ehxzim
INFO: gicv2: mmio: number of implemented SPIs: 256
PASS: gicv2: mmio: all 1 CPUs have interrupts
INFO: gicv2: mmio: IIDR: 0x
PASS: gicv2: mmio: GICD_TYPER is read-only
PASS: gicv2: mmio: GICD_IIDR is read-only
PASS: gicv2: mmio: ICPIDR2 is read-only (0x0004)
PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
PASS: gicv2: mmio: IPRIORITYR: clearing priorities
PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => )
PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x)
SUMMARY: 17 tests, 2 unexpected failures

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1
ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-48-generic aarch64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: arm64
Date: Tue May  7 11:25:30 2019
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug arm64 uec-images xenial
-- 
gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64
https://bugs.launchpad.net/bugs/1828026
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 1828351] Re: RAID 10 with MegaRaid controller gives poor write performance

[Nicolas Pochet]

Subscribing field-critical as it is blocking an ongoing deployment

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

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1828351

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

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

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

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

** Tags added: bionic

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

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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

[Kernel-packages] [Bug 1802492] Re: gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot ARM64 with Cosmic

[Po-Hsu Lin]

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

** This bug has been marked a duplicate of bug 1828026
   gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

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

Title:
  gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot ARM64 with Cosmic

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

Bug description:
  These two tests were skipped on Cavium ThunderX (QEMU Aborted)

  For gicv2-mmio-up

  # TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 
-machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.DQWZ285Qge
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 1 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x002b)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 
)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x)
  SUMMARY: 17 tests, 2 unexpected failures

  
  For gicv2-mmio-3p:
  # TESTNAME=gicv2-mmio-3p TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 
$((($MAX_SMP < 3)?$MAX_SMP:3)) -machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 2 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.LrtVFrCn2b
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 2 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x002b)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  FAIL: gicv2: mmio: ITARGETSR: bits for 6 non-existent CPUs masked
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (01030203 => 
0103020f)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01030203 => 0x02)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x011f020f)
  SUMMARY: 17 tests, 3 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  9 10:50 seq
   crw-rw 1 root audio 116, 33 Nov  9 10:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Nov  9 10:54:46 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  Rela

[Kernel-packages] [Bug 1828026] Re: gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

[Po-Hsu Lin]

Can be found on Disco as well.

** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

** Tags added: 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/1828026

Title:
  gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

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

Bug description:
  Failed on Moonshot nodes.

  
  FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

  # TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 
-machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.6k28Ehxzim
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 1 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x0004)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 
)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x)
  SUMMARY: 17 tests, 2 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1
  ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  Date: Tue May  7 11:25:30 2019
  SourcePackage: linux-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/1828026/+subscriptions

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

[Kernel-packages] [Bug 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

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

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Promote to Proposed
  phase-changed: Wednesday, 08. May 2019 17:12 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync

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

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

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

[elhoir]

Hello,

latest kernel 5.1.0  (lowlatency) from

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1/

Seems to have solved the issue, as i have started Ubuntu with no
problems with amdgpu module loaded.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1826036] Re: linux: 4.4.0-147.173 -proposed tracker

[Kleber Sacilotto de Souza]

Verification testing completed successfully with the Xenial kernel in
-proposed (https://kernel.ubuntu.com/reports/sru-report.html).

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

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

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

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

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

  backports: bug 1826034 (trusty/linux-aws), bug 1826035 
(trusty/linux-lts-xenial)
  derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 
(linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 26. April 2019 14:31 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
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1738263] Re: Touchpad not working and locking CPU

[Kai-Heng Feng]

Luke, please test this kernel:
https://people.canonical.com/~khfeng/lp1738263/

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

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Notebook: ASUS GL703VD
  Touchpad: probably ELAN clickpad

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

  the multitouch hid module take almost 100% of cpu and the mouse cursor
  moves badly (loosing it for a second or 2 then resuming) also feature
  clicks and doubleclicks and sensitivity problems.

  doing rmmod hid-multitouch.ko (or rmmod multitouch_hid) and
  blacklisting the module solves the cpu problem but obviously the
  touchoad is dead.

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

  (the touchpad works perfectly in windows 10 by the way)

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

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

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

[bugproxy]

--- Comment From klaus.theur...@de.ibm.com 2019-05-09 03:53 EDT---
Talked to Thomas Richter for a fresh Ubuntu 18.04 where we can test the 
provided changes, he will provide this image later today (tessia). I can't use 
the image where I found this issue for this 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/1828166

Title:
  perf top problem on z with Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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

[Kernel-packages] [Bug 1826036] Re: linux: 4.4.0-147.173 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1826034 (trusty/linux-aws), bug 1826035 
(trusty/linux-lts-xenial)
  derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 
(linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 26. April 2019 14:31 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
-   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/1826036

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

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

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

  backports: bug 1826034 (trusty/linux-aws), bug 1826035 
(trusty/linux-lts-xenial)
  derivatives: bug 1826024 (linux-aws), bug 1826028 (linux-kvm), bug 1826029 
(linux-raspi2), bug 1826030 (linux-snapdragon), bug 1826032 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 26. April 2019 14:31 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

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1828026

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

Title:
  gicv2-mmio-up in ubuntu_kvm_unit_tests failed on X-hwe ARM64

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

Bug description:
  Failed on Moonshot nodes.

  
  FAIL gicv2-mmio-up (17 tests, 2 unexpected failures)

  # TESTNAME=gicv2-mmio-up TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 1 
-machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 1 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.6k28Ehxzim
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 1 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x0004)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  PASS: gicv2: mmio: ITARGETSR: bits for 7 non-existent CPUs masked
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (01010001 => 
)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x01010001 => 0x00)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x)
  SUMMARY: 17 tests, 2 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51~16.04.1
  ProcVersionSignature: User Name 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  Date: Tue May  7 11:25:30 2019
  SourcePackage: linux-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/1828026/+subscriptions

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

[Kernel-packages] [Bug 1826029] Re: linux-raspi2: 4.4.0-1108.116 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-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: 1826036
  phase: Testing
  phase-changed: Friday, 03. May 2019 09:33 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

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

Title:
  linux-raspi2: 4.4.0-1108.116 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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:
  Fix Released
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: 1826036
  phase: Testing
  phase-changed: Friday, 03. May 2019 09:33 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

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

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

[Kernel-packages] [Bug 1811057] Re: global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests fails [X & B]

[Po-Hsu Lin]

This test passed on Disco / Cosmic

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

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

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

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

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

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

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1811057

Title:
  global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests
  fails [X & B]

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
   selftests: seccomp_bpf
   
   [==] Running 64 tests from 1 test cases.
   [ RUN  ] global.mode_strict_support
   [   OK ] global.mode_strict_support
   [ RUN  ] global.mode_strict_cannot_call_prctl
   [   OK ] global.mode_strict_cannot_call_prctl
   [ RUN  ] global.no_new_privs_support
   [   OK ] global.no_new_privs_support
   [ RUN  ] global.mode_filter_support
   [   OK ] global.mode_filter_support
   [ RUN  ] global.mode_filter_without_nnp
   [   OK ] global.mode_filter_without_nnp
   [ RUN  ] global.filter_size_limits
   [   OK ] global.filter_size_limits
   [ RUN  ] global.filter_chain_limits
   [   OK ] global.filter_chain_limits
   [ RUN  ] global.mode_filter_cannot_move_to_strict
   [   OK ] global.mode_filter_cannot_move_to_strict
   [ RUN  ] global.mode_filter_get_seccomp
   [   OK ] global.mode_filter_get_seccomp
   [ RUN  ] global.ALLOW_all
   [   OK ] global.ALLOW_all
   [ RUN  ] global.empty_prog
   [   OK ] global.empty_prog
   [ RUN  ] global.log_all
   [   OK ] global.log_all
   [ RUN  ] global.unknown_ret_is_kill_inside
   [   OK ] global.unknown_ret_is_kill_inside
   [ RUN  ] global.unknown_ret_is_kill_above_allow
   [   OK ] global.unknown_ret_is_kill_above_allow
   [ RUN  ] global.KILL_all
   [   OK ] global.KILL_all
   [ RUN  ] global.KILL_one
   [   OK ] global.KILL_one
   [ RUN  ] global.KILL_one_arg_one
   [   OK ] global.KILL_one_arg_one
   [ RUN  ] global.KILL_one_arg_six
   [   OK ] global.KILL_one_arg_six
   [ RUN  ] global.KILL_thread
   [==] Running 64 tests from 1 test cases.
   [ RUN  ] global.mode_strict_support
   [   OK ] global.mode_strict_support
   [ RUN  ] global.mode_strict_cannot_call_prctl
   [   OK ] global.mode_strict_cannot_call_prctl
   [ RUN  ] global.no_new_privs_support
   [   OK ] global.no_new_privs_support
   [ RUN  ] global.mode_filter_support
   [   OK ] global.mode_filter_support
   [ RUN  ] global.mode_filter_without_nnp
   [   OK ] global.mode_filter_without_nnp
   [ RUN  ] global.filter_size_limits
   [   OK ] global.filter_size_limits
   [ RUN  ] global.filter_chain_limits
   [   OK ] global.filter_chain_limits
   [ RUN  ] global.mode_filter_cannot_move_to_strict
   [   OK ] global.mode_filter_cannot_move_to_strict
   [ RUN  ] global.mode_filter_get_seccomp
   [   OK ] global.mode_filter_get_seccomp
   [ RUN  ] global.ALLOW_all
   [   OK ] global.ALLOW_all
   [ RUN  ] global.empty_prog
   [   OK ] global.empty_prog
   [ RUN  ] global.log_all
   [   OK ] global.log_all
   [ RUN  ] global.unknown_ret_is_kill_inside
   [   OK ] global.unknown_ret_is_kill_inside
   [ RUN  ] global.unknown_ret_is_kill_above_allow
   [   OK ] global.unknown_ret_is_kill_above_allow
   [ RUN  ] global.KILL_all
   [   OK ] global.KILL_all
   [ RUN  ] global.KILL_one
   [   OK ] global.KILL_one
   [ RUN  ] global.KILL_one_arg_one
   [   OK ] global.KILL_one_arg_one
   [ RUN  ] global.KILL_one_arg_six
   [   OK ] global.KILL_one_arg_six
   [ RUN  ] global.KILL_thread
   [   OK ] global.KILL_thread
   [ RUN  ] global.KILL_process
   [   OK ] global.KILL_process
   [ RUN  ] global.arg_out_of_range
   [   OK ] global.arg_out_of_range
   [ RUN  ] global.ERRNO_valid
   [   OK ] global.ERRNO_valid
   [ RUN  ] global.ERRNO_zero
   [   OK ] global.ERRNO_zero
   [ RUN  ] global.ERRNO_capped
   [   OK ] global.ERRNO_capped
   [ RUN  ] global.ERRNO_order
   [   OK ] global.ERRNO_order
   [ RUN  ] TRAP.dfl
   [   OK ] TRAP.dfl
   [ RUN  ] TR

[Kernel-packages] [Bug 1826024] Re: linux-aws: 4.4.0-1082.92 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-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: 1826036
  phase: Signoff
  phase-changed: Monday, 06. May 2019 05:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-updates: Holding -- security signoff not verified
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/1826024

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Signoff
  phase-changed: Monday, 06. May 2019 05:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826028] Re: linux-kvm: 4.4.0-1045.51 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-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: 1826036
  phase: Signoff
  phase-changed: Saturday, 27. April 2019 12:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-updates: Holding -- security signoff not verified
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/1826028

Title:
  linux-kvm: 4.4.0-1045.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  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:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1826036
  phase: Signoff
  phase-changed: Saturday, 27. April 2019 12:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1812636] Re: Kprobe probing module in ftrace from ubuntu_kernel_selftest failed on B/C

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Committed

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

Title:
  Kprobe probing module in ftrace from ubuntu_kernel_selftest failed on
  B/C

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  This test:
  [27] Kprobe dynamic event - probing module[FAIL]

  Failed in the ftrace test of the ubuntu_kernel_selftests on Bionic and
  Cosmic ARM64 / i386 (passed with AMD64 / Power8 / Power9 / s390x)

  $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  TAP version 13
  selftests: ftracetest
  
  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] event tracing - enable/disable with event level files [PASS]
  [6] event tracing - restricts events based on pid [PASS]
  [7] event tracing - enable/disable with subsystem level files [PASS]
  [8] event tracing - enable/disable with top level files   [PASS]
  [9] ftrace - function graph filters with stack tracer [PASS]
  [10] ftrace - function graph filters  [PASS]
  [11] ftrace - function glob filters   [PASS]
  [12] ftrace - function pid filters[PASS]
  [13] ftrace - test for function event triggers[PASS]
  [14] ftrace - function profiler with function tracing [PASS]
  [15] ftrace - test reading of set_ftrace_filter   [PASS]
  [16] ftrace - test for function traceon/off triggers  [PASS]
  [17] Test creation and deletion of trace instances while setting an event 
[PASS]
  [18] Test creation and deletion of trace instances[PASS]
  [19] Kprobe dynamic event - adding and removing   [PASS]
  [20] Kprobe dynamic event - busy event check  [PASS]
  [21] Kprobe dynamic event with arguments  [PASS]
  [22] Kprobe event string type argument[PASS]
  [23] Kprobe event argument syntax [PASS]
  [24] Kprobes event arguments with types   [PASS]
  [25] Kprobe event auto/manual naming  [PASS]
  [26] Kprobe dynamic event with function tracer[PASS]
  [27] Kprobe dynamic event - probing module[FAIL]
  [28] Kretprobe dynamic event with arguments   [PASS]
  [29] Kretprobe dynamic event with maxactive   [PASS]
  [30] Register/unregister many kprobe events   [PASS]
  [31] Kprobe events - probe points [PASS]
  [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED]
  [33] event trigger - test event enable/disable trigger[PASS]
  [34] event trigger - test trigger filter  [PASS]
  [35] event trigger - test histogram modifiers [PASS]
  [36] event trigger - test histogram trigger   [PASS]
  [37] event trigger - test multiple histogram triggers [PASS]
  [38] event trigger - test snapshot-trigger[PASS]
  [39] event trigger - test stacktrace-trigger  [PASS]
  [40] event trigger - test traceon/off trigger [PASS]
  [41] (instance)  Basic test for tracers   [PASS]
  [42] (instance)  Basic trace clock test   [PASS]
  [43] (instance)  event tracing - enable/disable with event level files
[PASS]
  [44] (instance)  event tracing - restricts events based on pid[PASS]
  [45] (instance)  event tracing - enable/disable with subsystem level files
[PASS]
  [46] (instance)  ftrace - test for function event triggers[PASS]
  [47] (instance)  ftrace - test for function traceon/off triggers  [PASS]
  [48] (instance)  event trigger - test event enable/disable trigger[PASS]
  [49] (instance)  event trigger - test trigger filter  [PASS]
  [50] (instance)  event trigger - test histogram modifiers [PASS]
  [51] (instance)  event trigger - test histogram trigger   [PASS]
  [52] (instance)  event trigger - test multiple histogram triggers [PASS]

  # of passed:  50
  # of failed:  1
  # of unresolved:  0
  # of untested:  0
  # of unsupported:  1
  # of xfailed:  0
  # of undefined(test bug):  0
  not ok 1..1 selftests:  ftracetest [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.

[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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: 1826036
  phase: Promote to Proposed
  phase-changed: Wednesday, 08. May 2019 16:34 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync

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

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

[Kernel-packages] [Bug 1826030] Re: linux-snapdragon: 4.4.0-1112.117 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/verification-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: 1826036
  phase: Signoff
  phase-changed: Wednesday, 08. May 2019 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-updates: Holding -- security signoff not verified
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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1826030

Title:
  linux-snapdragon: 4.4.0-1112.117 -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 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1826036
  phase: Signoff
  phase-changed: Wednesday, 08. May 2019 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1811057] Re: global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests fails [X & B]

[Po-Hsu Lin]

With upstream tree, this test still failed on Bionic:
[ RUN  ] global.get_metadata
seccomp_bpf.c:3034:global.get_metadata:Expected sizeof(md) (16) == ret 
(18446744073709551615)
seccomp_bpf.c:3039:global.get_metadata:Expected md.flags (0) == 
SECCOMP_FILTER_FLAG_LOG (2)
seccomp_bpf.c:3044:global.get_metadata:Expected sizeof(md) (16) == ret 
(18446744073709551615)
global.get_metadata: Test failed at step #6
[ FAIL ] global.get_metadata

As this test has passed with 4.18 kernel on Bionic, it looks like a
kernel issue to me.

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

Title:
  global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests
  fails [X & B]

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
   selftests: seccomp_bpf
   
   [==] Running 64 tests from 1 test cases.
   [ RUN  ] global.mode_strict_support
   [   OK ] global.mode_strict_support
   [ RUN  ] global.mode_strict_cannot_call_prctl
   [   OK ] global.mode_strict_cannot_call_prctl
   [ RUN  ] global.no_new_privs_support
   [   OK ] global.no_new_privs_support
   [ RUN  ] global.mode_filter_support
   [   OK ] global.mode_filter_support
   [ RUN  ] global.mode_filter_without_nnp
   [   OK ] global.mode_filter_without_nnp
   [ RUN  ] global.filter_size_limits
   [   OK ] global.filter_size_limits
   [ RUN  ] global.filter_chain_limits
   [   OK ] global.filter_chain_limits
   [ RUN  ] global.mode_filter_cannot_move_to_strict
   [   OK ] global.mode_filter_cannot_move_to_strict
   [ RUN  ] global.mode_filter_get_seccomp
   [   OK ] global.mode_filter_get_seccomp
   [ RUN  ] global.ALLOW_all
   [   OK ] global.ALLOW_all
   [ RUN  ] global.empty_prog
   [   OK ] global.empty_prog
   [ RUN  ] global.log_all
   [   OK ] global.log_all
   [ RUN  ] global.unknown_ret_is_kill_inside
   [   OK ] global.unknown_ret_is_kill_inside
   [ RUN  ] global.unknown_ret_is_kill_above_allow
   [   OK ] global.unknown_ret_is_kill_above_allow
   [ RUN  ] global.KILL_all
   [   OK ] global.KILL_all
   [ RUN  ] global.KILL_one
   [   OK ] global.KILL_one
   [ RUN  ] global.KILL_one_arg_one
   [   OK ] global.KILL_one_arg_one
   [ RUN  ] global.KILL_one_arg_six
   [   OK ] global.KILL_one_arg_six
   [ RUN  ] global.KILL_thread
   [==] Running 64 tests from 1 test cases.
   [ RUN  ] global.mode_strict_support
   [   OK ] global.mode_strict_support
   [ RUN  ] global.mode_strict_cannot_call_prctl
   [   OK ] global.mode_strict_cannot_call_prctl
   [ RUN  ] global.no_new_privs_support
   [   OK ] global.no_new_privs_support
   [ RUN  ] global.mode_filter_support
   [   OK ] global.mode_filter_support
   [ RUN  ] global.mode_filter_without_nnp
   [   OK ] global.mode_filter_without_nnp
   [ RUN  ] global.filter_size_limits
   [   OK ] global.filter_size_limits
   [ RUN  ] global.filter_chain_limits
   [   OK ] global.filter_chain_limits
   [ RUN  ] global.mode_filter_cannot_move_to_strict
   [   OK ] global.mode_filter_cannot_move_to_strict
   [ RUN  ] global.mode_filter_get_seccomp
   [   OK ] global.mode_filter_get_seccomp
   [ RUN  ] global.ALLOW_all
   [   OK ] global.ALLOW_all
   [ RUN  ] global.empty_prog
   [   OK ] global.empty_prog
   [ RUN  ] global.log_all
   [   OK ] global.log_all
   [ RUN  ] global.unknown_ret_is_kill_inside
   [   OK ] global.unknown_ret_is_kill_inside
   [ RUN  ] global.unknown_ret_is_kill_above_allow
   [   OK ] global.unknown_ret_is_kill_above_allow
   [ RUN  ] global.KILL_all
   [   OK ] global.KILL_all
   [ RUN  ] global.KILL_one
   [   OK ] global.KILL_one
   [ RUN  ] global.KILL_one_arg_one
   [   OK ] global.KILL_one_arg_one
   [ RUN  ] global.KILL_one_arg_six
   [   OK ] global.KILL_one_arg_six
   [ RUN  ] global.KILL_thread
   [   OK ] global.KILL_thread
   [ RUN  ] global.KILL_process
   [   OK ] global.KILL_process
   [ RUN  ] global.arg_out_of_range
   [   OK ] global.arg_out_of_range
   [ RUN  ] global.ERRNO_valid
   [   OK ] global.ERRNO_valid
   [ RUN  ] global.ERRNO_zero
   [   OK ] global.ERRNO_zero
   [ RUN  ] global.ERRNO_capped
   [   OK ] global.ERRNO_capped
   [ RUN  ] global.ERRNO_order
   [   OK ] global.ERRNO_order
   [ RUN  ] TRAP.dfl
   [   OK ] TRAP.dfl
   [ RUN  ] TRAP.ign
   [   OK ] TRAP.ign
   

[Kernel-packages] [Bug 1826716] Re: Include Sunix serial/parallel driver

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Include Sunix serial/parallel driver

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  [Impact]
  We shipped several platform with sunix device, which is enabled by sunix
  DKMS driver.
  We should use in-tree driver instead.

  [Fix]
  Include not-yet-merged sunix driver:
  https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/

  [Test]
  Use command `inputattach` to test serial mouse connected to the Sunix
  board. The mouse works correctly. 

  [Regression Potential]
  Low. It's a new driver so the regression potential is minimal.

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ł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/1826034

Title:
  linux-aws: 4.4.0-1043.46 -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: 1826036
  phase: Promote to Proposed
  phase-changed: Thursday, 09. May 2019 08:34 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/1826034/+subscriptions

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

[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on Cosmic ARM64

[Po-Hsu Lin]

For Disco, 
passed on ThunderX
failed on Moonshot

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

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

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

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

** Tags added: 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/1805806

Title:
  test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
  timeout" on Cosmic ARM64

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

Bug description:
  This issue can be found on 2 different ARM64 node, TunderX Cavium node
  "starmie" and Moonshot "ms10-34-mcdivittB0-kernel"

  Running test_maps bpf test..
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'

[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on Cosmic ARM64

[Po-Hsu Lin]

For Disco,
failed on ThunderX (1 out of 2 runs)
failed on Moonshot

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

Title:
  test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
  timeout" on Cosmic ARM64

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

Bug description:
  This issue can be found on 2 different ARM64 node, TunderX Cavium node
  "starmie" and Moonshot "ms10-34-mcdivittB0-kernel"

  Running test_maps bpf test..
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Fork 1024 tasks to 'test_update_delete'
    Fork 1024 tasks to 'test_update_delete'
    Fork 100 tasks to 'test_hashmap'
    Fork 100 tasks to 'test_hashmap_percpu'
    Fork 100 tasks to 'test_hashmap_sizes'
    Fork 100 tasks to 'test_hashmap_walk'
    Fork 100 tasks to 'test_arraymap'
    Fork 100 tasks to 'test_arraymap_percpu'
    Failed sockmap unexpected timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.

[Kernel-packages] [Bug 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine

[Yuan-Chen Cheng]

** Tags added: oem-priority

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

Title:
  The noise keeps occurring when Headset is plugged in on a Dell machine

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Plug in headset
  2. Select Headset mode

  Expected result:
  There is no noise when headset is plugged in

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 07. May 2019 12:04 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 09. May 2019 08:34 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1826034

Title:
  linux-aws: 4.4.0-1043.46 -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: 1826036
  phase: Promote to Proposed
  phase-changed: Thursday, 09. May 2019 08:34 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/1826034/+subscriptions

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

[Kernel-packages] [Bug 1769120] Re: [Dell Precision 5520] wifi is very unreliable to connect over b and g protocol

[Yuan-Chen Cheng]

given no activity, remove from oem-priority.

** No longer affects: oem-priority

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

Title:
  [Dell Precision 5520] wifi is very unreliable to connect over b and g
  protocol

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell Precision 5520 (CID 201610-25144)
  pre-installed (oem) image (16.04)

  [Description]

  When the wifi tries to connect SSID over b and g protocol, it is very
  hard to build connection successfully. The reproducing rate is 9/10.

  [Steps to Reproduce]

  1. Update the system to use the last stack.
  2. Reboot
  3. Connect the bg wifi by network-manager applet

  [Expected Result]

  The network-manager builds the connection.

  [Actual Result]

  The network-manger could not connect to the target SSID.





  
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-123-generic 4.4.0-123.147
  ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128
  Uname: Linux 4.4.0-123-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1972 F pulseaudio
  Date: Fri May  4 19:16:50 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=395dc72d-da55-4d11-8875-2240537ead7f
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-123-generic.efi.signed 
root=UUID=f71a7ab1-fcc5-4873-839b-1b7955196b53 ro automatic-oem-config quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-123-generic N/A
   linux-backports-modules-4.4.0-123-generic  N/A
   linux-firmware 1.157.18
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746411] Re: [linux-oem] Fix out of bound VBT pin on CNP

[Yuan-Chen Cheng]

** Tags added: hwe oem-priority

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

Title:
  [linux-oem] Fix out of bound VBT pin on CNP

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  i915 crashed when probing for VBT pin. No graphics output after that.

  [Test Case]
  Enable Legacy ROM boot option in BIOS. Screen goes blank.
  Cherrypick fixes can solve the issue. 

  [Fix]
  Handle out of bounds pin value more appropriately.
  Patches from Jani are most refactoring, but the fix we want depends on
  them.
  Patches from Rogrigo are the fixes we want. These patches are also
  picked base on his suggestion,
  https://bugs.freedesktop.org/show_bug.cgi?id=104139#c7

  [Regression Potential]
  Low. CNL and CNP are still quite new. These commits are limited to them.

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ł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/1826034

Title:
  linux-aws: 4.4.0-1043.46 -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 Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1826036
  phase: Holding before Testing
  phase-changed: Thursday, 09. May 2019 09:04 UTC

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

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

[Kernel-packages] [Bug 1828302] Re: CSR Bluetooth driver: Insufficient performance compared to WIndows driver

[Luca Mastromatteo]

Ok I did some further testing, and it looks like the issue comes out
when those two conditions are met:

Using Ubuntu Linux + Using front USB 3.0 ports on my desktop.

The issue DOES NOT happen (or so it looks like) when I use the back mobo
3.1 USB ports, or I use my laptop, which again has USB 3.1 USB ports.

And DOES NOT happen on Windows, with any USB port used on my desktop.

So maybe it's something hub driver-related?

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

Title:
  CSR Bluetooth driver: Insufficient performance compared to WIndows
  driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm reporting this because I'm pretty sure a class 2 bluetooth adapter
  shouldn't be unable to connect at less than 1 meter, when comparing
  this to the Windows driver at least...

  The bluetooth device is a CSR USB bluetooth 2.1 adapter

  hci1: Type: Primary  Bus: USB
   BD Address: 00:15:83:xx:xx:xx  ACL MTU: 310:10  SCO MTU: 64:8
   UP RUNNING PSCAN
   RX bytes:667 acl:0 sco:0 events:49 errors:0
   TX bytes:4783 acl:0 sco:0 commands:48 errors:0
   Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'luky-XPS-15-9550 #2
   Class: 0x3c010c
   Service Classes: Rendering, Capturing, Object Transfer, Audio
   Device Class: Computer, Laptop
   HCI Version: 2.1 (0x4)  Revision: 0x149c
   LMP Version: 2.1 (0x4)  Subversion: 0x149c
   Manufacturer: Cambridge Silicon Radio (10)

  the kernel driver in use is `btusb`
  the ubuntu version is 19.04
  the kernel version is 5.0.0-13-generic

  In Windows this adapter work normally, on Ubuntu Linux it's barely
  able to connect to any device and maintain a stable connection, it
  completely loses the connection unlikely in Windows after more than 40
  centimeters

  Already tried the 5.1 mainline kernel, it doesn't seem different

  Worth noting that I also tried this on my laptop, and here looks like
  it works insanely better than my desktop pc...

  My desktop PC has a Ryzen 5 1600 CPU, and an MSI b350 mobo
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luky   1581 F pulseaudio
   /dev/snd/controlC1:  luky   1581 F pulseaudio
   /dev/snd/pcmC1D0c:   luky   1581 F...m pulseaudio
   /dev/snd/controlC2:  luky   1581 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-07 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 
(20190416)
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=5756c217-a2d2-4100-b7c1-b38264030191 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.K0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR (MS-7A37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
- phase: Promote to Proposed
- phase-changed: Thursday, 09. May 2019 08:34 UTC
- reason:
-   promote-to-proposed: Ongoing -- review in progress
+ phase: Holding before Testing
+ phase-changed: Thursday, 09. May 2019 09:04 UTC

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

Title:
  linux-aws: 4.4.0-1043.46 -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 Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1826036
  phase: Holding before Testing
  phase-changed: Thursday, 09. May 2019 09:04 UTC

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

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

[Kernel-packages] [Bug 1796634] Re: [0cf3:e007] Can't turn on BT by Wireless hotkey

[Yuan-Chen Cheng]

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

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

Title:
  [0cf3:e007] Can't turn on BT by Wireless hotkey

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in Gaming Edition:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The issue has been found on new Dell laptop with DW1820 combo card(BT is 
[0cf3:e007])
  1) Use wireless hotkey to turn off WiFi/BT.
  2) Wait 5 minutes.
  3) Use wireless hotkey to turn on WiFi/BT.
  4) Wifi is back, but BT is still off
  5) Only reboot can recovery the BT state

  [Fix]
  Qualcomm releases a new firmware to fix it.

  [Regression Potential]
  Can't evaluate it, but from our verification and S3 stress test,
  there is no any issues result from the firmwares.

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

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

[Kernel-packages] [Bug 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine

[Yuan-Chen Cheng]

** Tags added: hwe

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

Title:
  The noise keeps occurring when Headset is plugged in on a Dell machine

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Plug in headset
  2. Select Headset mode

  Expected result:
  There is no noise when headset is plugged in

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

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

[Kernel-packages] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]

[Yuan-Chen Cheng]

** Tags added: hwe oem-priority

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

Title:
  Intel I210 Ethernet card not working after hotplug [8086:1533]

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Summary:
  Intel I210 Ethernet card not working after hotplug

  Steps to reproduce:
  1. Power on system with ethernet cable on Intel I210
  2. Check ethernet is workable
  3. Unplug then plug the ethernet cable

  Expected result:
  Intel I210 Ethernet card is working, e.g. IP address acquired automatically 
if configured as DHCP.

  Actual result:
  Intel I210 Ethernet card not working after hotplug. dmesg has following error 
messages instead:
  [ 16.464321] [ cut here ]
  [ 16.464326] PCI PM: State of device not saved by 
igb_runtime_suspend+0x0/0x90 [igb]
  [ 16.464334] WARNING: CPU: 2 PID: 49 at 
/build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 
pci_pm_runtime_suspend+0x175/0x180
  [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel 
irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep 
ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 
snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi 
intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas 
snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd 
sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci 
intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
  [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect 
i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi 
video
  [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem 
#37-Ubuntu
  [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 
01/14/2019
  [ 16.464369] Workqueue: pm pm_runtime_work
  [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180
  [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282
  [ 16.464372] RAX:  RBX: 8a2557aee0a0 RCX: 0006
  [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490
  [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373
  [ 16.464373] R10:  R11:  R12: 
  [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: 
  [ 16.464374] FS: () GS:8a257c48() 
knlGS:
  [ 16.464375] CS: 0010 DS:  ES:  CR0: 80050033
  [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0
  [ 16.464376] DR0:  DR1:  DR2: 
  [ 16.464376] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 16.464376] Call Trace:
  [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464380] __rpm_callback+0xca/0x210
  [ 16.464381] ? __switch_to_asm+0x40/0x70
  [ 16.464382] ? __switch_to_asm+0x34/0x70
  [ 16.464382] rpm_callback+0x59/0x80
  [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464384] rpm_suspend+0x137/0x640
  [ 16.464385] ? __switch_to_asm+0x40/0x70
  [ 16.464386] pm_runtime_work+0x81/0xa0
  [ 16.464388] process_one_work+0x1de/0x410
  [ 16.464389] worker_thread+0x32/0x410
  [ 16.464390] kthread+0x121/0x140
  [ 16.464391] ? process_one_work+0x410/0x410
  [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70
  [ 16.464392] ret_from_fork+0x35/0x40
  [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b 
b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b 
e9 fd fe ff ff 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53
  [ 16.464408] ---[ end trace 97e5f2cf651b62e6 ]---

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

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

[Kernel-packages] [Bug 1811057] Re: global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests fails [X & B]

[Po-Hsu Lin]

It turns out that the seccomp in Bionic does not support seccomp
metadata retrieval.

These commits are needed for Bionic to enable metadata retrieval:
26500475ac1b499d8636ff281311d633909f5d20
f06eae831f0c1fc5b982ea200daf552810e1dd55

This will reduce the failure to:
  [ RUN  ] global.get_metadata
  seccomp_bpf.c:3046:global.get_metadata:Expected md.filter_off (0) == 1 (1)
  global.get_metadata: Test failed at step #6

And this one can be fixed with:
63bb0045b98ae821e56e27c2250e14bb0ae663e5

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests
  fails [X & B]

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
   selftests: seccomp_bpf
   
   [==] Running 64 tests from 1 test cases.
   [ RUN  ] global.mode_strict_support
   [   OK ] global.mode_strict_support
   [ RUN  ] global.mode_strict_cannot_call_prctl
   [   OK ] global.mode_strict_cannot_call_prctl
   [ RUN  ] global.no_new_privs_support
   [   OK ] global.no_new_privs_support
   [ RUN  ] global.mode_filter_support
   [   OK ] global.mode_filter_support
   [ RUN  ] global.mode_filter_without_nnp
   [   OK ] global.mode_filter_without_nnp
   [ RUN  ] global.filter_size_limits
   [   OK ] global.filter_size_limits
   [ RUN  ] global.filter_chain_limits
   [   OK ] global.filter_chain_limits
   [ RUN  ] global.mode_filter_cannot_move_to_strict
   [   OK ] global.mode_filter_cannot_move_to_strict
   [ RUN  ] global.mode_filter_get_seccomp
   [   OK ] global.mode_filter_get_seccomp
   [ RUN  ] global.ALLOW_all
   [   OK ] global.ALLOW_all
   [ RUN  ] global.empty_prog
   [   OK ] global.empty_prog
   [ RUN  ] global.log_all
   [   OK ] global.log_all
   [ RUN  ] global.unknown_ret_is_kill_inside
   [   OK ] global.unknown_ret_is_kill_inside
   [ RUN  ] global.unknown_ret_is_kill_above_allow
   [   OK ] global.unknown_ret_is_kill_above_allow
   [ RUN  ] global.KILL_all
   [   OK ] global.KILL_all
   [ RUN  ] global.KILL_one
   [   OK ] global.KILL_one
   [ RUN  ] global.KILL_one_arg_one
   [   OK ] global.KILL_one_arg_one
   [ RUN  ] global.KILL_one_arg_six
   [   OK ] global.KILL_one_arg_six
   [ RUN  ] global.KILL_thread
   [==] Running 64 tests from 1 test cases.
   [ RUN  ] global.mode_strict_support
   [   OK ] global.mode_strict_support
   [ RUN  ] global.mode_strict_cannot_call_prctl
   [   OK ] global.mode_strict_cannot_call_prctl
   [ RUN  ] global.no_new_privs_support
   [   OK ] global.no_new_privs_support
   [ RUN  ] global.mode_filter_support
   [   OK ] global.mode_filter_support
   [ RUN  ] global.mode_filter_without_nnp
   [   OK ] global.mode_filter_without_nnp
   [ RUN  ] global.filter_size_limits
   [   OK ] global.filter_size_limits
   [ RUN  ] global.filter_chain_limits
   [   OK ] global.filter_chain_limits
   [ RUN  ] global.mode_filter_cannot_move_to_strict
   [   OK ] global.mode_filter_cannot_move_to_strict
   [ RUN  ] global.mode_filter_get_seccomp
   [   OK ] global.mode_filter_get_seccomp
   [ RUN  ] global.ALLOW_all
   [   OK ] global.ALLOW_all
   [ RUN  ] global.empty_prog
   [   OK ] global.empty_prog
   [ RUN  ] global.log_all
   [   OK ] global.log_all
   [ RUN  ] global.unknown_ret_is_kill_inside
   [   OK ] global.unknown_ret_is_kill_inside
   [ RUN  ] global.unknown_ret_is_kill_above_allow
   [   OK ] global.unknown_ret_is_kill_above_allow
   [ RUN  ] global.KILL_all
   [   OK ] global.KILL_all
   [ RUN  ] global.KILL_one
   [   OK ] global.KILL_one
   [ RUN  ] global.KILL_one_arg_one
   [   OK ] global.KILL_one_arg_one
   [ RUN  ] global.KILL_one_arg_six
   [   OK ] global.KILL_one_arg_six
   [ RUN  ] global.KILL_thread
   [   OK ] global.KILL_thread
   [ RUN  ] global.KILL_process
   [   OK ] global.KILL_process
   [ RUN  ] global.arg_out_of_range
   [   OK ] global.arg_out_of_range
   [ RUN  ] global.ERRNO_valid
   [   OK ] global.ERRNO_valid
   [ RU

[Kernel-packages] [Bug 1826350] Re: linux-fips: 4.15.0-1006.7 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
- phase: Promote to Proposed
- phase-changed: Wednesday, 08. May 2019 17:12 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 09. May 2019 09:11 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
  phase: Ready for Testing
  phase-changed: Thursday, 09. May 2019 09:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake

[Anthony Wong]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Tags added: icelake

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

Title:
  [ICL] Enable intel_rapl driver for Icelake

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Desription:
  This feature is intended to track intel_rapl driver enabling for IceLake.

  Commit:Powercap/intel_rapl driver enabling for Icelake

  Target Release: 19.10
  Target Kernel: 5.1

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

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

[Kernel-packages] [Bug 1819413] Re: [ICL] S0ix Enabling

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Tags added: icelake

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

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

Title:
  [ICL] S0ix Enabling

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:

  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.

  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;

  (2) by runtime PM, i.e no system activities with display off.

  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.

   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine

  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM

  Both paths will require intel_idle driver support for S0ix support.

  238f9c11351f8af8534ae0318b4d9acc77b09ee8

  8aba056a4ea6da18186025a335a96b2f071e69d3

  6769fdbe27d782dfee5e459e25b44baacc7c8459

  cfb55af9add9c19806300fdb31f4cd25e67c6d1a

  4a5861f714293767980e4948c9a7c9e5e09c9b94

  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b

  cd89e92b7399a69512b8d855a2dd145c47399bf8

  d6827015e671cd17871c9b7a0fabe06c044f7470

  0e68eeea9894feeba2edf7ec63e4551b87f39621

  e50af8332785355de3cb40d9f5e8c45dbfc86f53

  Target Kernel: 5.1
  Target Release: 19.10

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

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

[Kernel-packages] [Bug 1822235] Re: All 29 tests in kvm-unit-test failed (timeouted) on i386

[Po-Hsu Lin]

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

Title:
  All 29 tests in kvm-unit-test failed (timeouted) on i386

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

Bug description:
  All the available tests in kvm-unit-test have failed on Cosmic i386 with node 
"onza".
  They all timeout with the default 90 second threshold.

   TESTNAME=smptest TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 2
   FAIL smptest (timeout; duration=90s)
   TESTNAME=smptest3 TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 3
   FAIL smptest3 (timeout; duration=90s)
   TESTNAME=vmexit_cpuid TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 
-append 'cpuid'
   FAIL vmexit_cpuid (timeout; duration=90s)
   TESTNAME=vmexit_vmcall TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 
-append 'vmcall'
   FAIL vmexit_vmcall (timeout; duration=90s)
   TESTNAME=vmexit_mov_from_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat 
-smp 1 -append 'mov_from_cr8'
   FAIL vmexit_mov_from_cr8 (timeout; duration=90s)
   TESTNAME=vmexit_mov_to_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 
1 -append 'mov_to_cr8'
   FAIL vmexit_mov_to_cr8 (timeout; duration=90s)
   TESTNAME=vmexit_inl_pmtimer TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat 
-smp 1 -append 'inl_from_pmtimer'
   FAIL vmexit_inl_pmtimer (timeout; duration=90s)
   TESTNAME=vmexit_ipi TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 
-append 'ipi'
   FAIL vmexit_ipi (timeout; duration=90s)
   TESTNAME=vmexit_ipi_halt TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 
-append 'ipi_halt'
   FAIL vmexit_ipi_halt (timeout; duration=90s)
   TESTNAME=vmexit_ple_round_robin TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat 
-smp 1 -append 'ple_round_robin'
   FAIL vmexit_ple_round_robin (timeout; duration=90s)
   TESTNAME=vmexit_tscdeadline TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat 
-smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline
   FAIL vmexit_tscdeadline (timeout; duration=90s)
   TESTNAME=vmexit_tscdeadline_immed TIMEOUT=90s ACCEL= ./x86/run 
x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append 
tscdeadline_immed
   FAIL vmexit_tscdeadline_immed (timeout; duration=90s)
   TESTNAME=smap TIMEOUT=90s ACCEL= ./x86/run x86/smap.flat -smp 1 -cpu host
   FAIL smap (timeout; duration=90s)
   TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1
   FAIL eventinj (timeout; duration=90s)
   TESTNAME=hypercall TIMEOUT=90s ACCEL= ./x86/run x86/hypercall.flat -smp 1
   FAIL hypercall (timeout; duration=90s)
   TESTNAME=msr TIMEOUT=90s ACCEL= ./x86/run x86/msr.flat -smp 1
   FAIL msr (timeout; duration=90s)
   TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1
   FAIL port80 (timeout; duration=90s)
   TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1
   FAIL realmode (timeout; duration=90s)
   TESTNAME=s3 TIMEOUT=90s ACCEL= ./x86/run x86/s3.flat -smp 1
   FAIL s3 (timeout; duration=90s)
   TESTNAME=sieve TIMEOUT=90s ACCEL= ./x86/run x86/sieve.flat -smp 1
   FAIL sieve (timeout; duration=90s)
   TESTNAME=tsc TIMEOUT=90s ACCEL= ./x86/run x86/tsc.flat -smp 1 -cpu 
kvm64,+rdtscp
   FAIL tsc (timeout; duration=90s)
   TESTNAME=tsc_adjust TIMEOUT=90s ACCEL= ./x86/run x86/tsc_adjust.flat -smp 1 
-cpu host
   FAIL tsc_adjust (timeout; duration=90s)
   TESTNAME=taskswitch TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch.flat -smp 1
   FAIL taskswitch (timeout; duration=90s)
   TESTNAME=taskswitch2 TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch2.flat -smp 1
   FAIL taskswitch2 (timeout; duration=90s)
   TESTNAME=kvmclock_test TIMEOUT=90s ACCEL= ./x86/run x86/kvmclock_test.flat 
-smp 2 --append "1000 `date +%s`"
   FAIL kvmclock_test (timeout; duration=90s)
   TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu 
qemu64,+umip
   FAIL umip (timeout; duration=90s)
   TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat 
-smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev
   FAIL hyperv_synic (timeout; duration=90s)
   TESTNAME=hyperv_connections TIMEOUT=90s ACCEL= ./x86/run 
x86/hyperv_connections.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device 
hyperv-testdev
   FAIL hyperv_connections (timeout; duration=90s)
   TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat 
-smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev
   FAIL hyperv_stimer (timeout; duration=90s)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-16-generic 4.18.0-16.17
  ProcVersionSignature: User Name 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-ge

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Łukasz Zemczak]

Ok, in that case this seems like a verification-failed. @cascardo can
you follow up on this SRU?

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

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system

  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie
  Mitsuyoshi/carri...@us.ibm.com

  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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

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

[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Changed in: kernel-sru-workflow/verification-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: 1826036
- phase: Promote to Proposed
- phase-changed: Wednesday, 08. May 2019 16:34 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 09. May 2019 09:34 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Pending -- Ready

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Ready for Testing
  phase-changed: Thursday, 09. May 2019 09:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Pending -- Ready

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

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

[Kernel-packages] [Bug 1826352] Re: linux-azure: 4.15.0-1044.48~14.04.1 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux-azure: 4.15.0-1044.48~14.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-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1826354
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 09. May 2019 09:44 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1826352] Re: linux-azure: 4.15.0-1044.48~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-signing-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: 1826354
- phase: Holding before Testing
- phase-changed: Wednesday, 08. May 2019 14:43 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 09. May 2019 09:44 UTC
+ reason:
+   promote-signing-to-proposed: Pending -- ready for review

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

Title:
  linux-azure: 4.15.0-1044.48~14.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-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1826354
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 09. May 2019 09:44 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-signing-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: 1826036
- phase: Holding before Testing
- phase-changed: Thursday, 09. May 2019 09:04 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 09. May 2019 09:43 UTC
+ reason:
+   promote-signing-to-proposed: Pending -- ready for review

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1826036
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 09. May 2019 09:43 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Andy Whitcroft]

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1826036
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 09. May 2019 09:43 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1828380] [NEW] f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386

[Po-Hsu Lin]

Public bug reported:

Test failed with:
  btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43


Test log:
  * Command: 
  BINDIR=/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes /home
  /ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/ubuntu_btrfs_kerne
  l_fixes.sh /home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/fi
  xes/f88ba6a2a44ee98e8d59654463dc157bb6d13c43.sh 2>&1
  Exit status: 1
  Duration: 11.0287649632
  
  stdout:
  Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  
  fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  
  Btrfs: skip submitting barrier for missing device
  
  I got an error on v3.13:
   BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure 
(errors while submitting device barriers.)
  
  how to reproduce:
> mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
> wipefs -a /dev/sdf2
> mount -o degraded /dev/sdf1 /mnt
> btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt
  
  The reason of the error is that barrier_all_devices() failed to submit
  barrier to the missing device.  However it is clear that we cannot do
  anything on missing device, and also it is not necessary to care chunks
  on the missing device.
  
  This patch stops sending/waiting barrier if device is missing.
  
  btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  
  FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)


Syslog:
kernel: [ 1531.598180] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
kernel: [ 1531.822544] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 
devid 1 transid 5 /dev/loop2 
kernel: [ 1531.917840] BTRFS: device fsid 28683721-4c7a-4922-a753-e61ca95c0726 
devid 2 transid 5 /dev/loop3 
kernel: [ 1532.314274] BTRFS info (device loop2): allowing degraded mounts
kernel: [ 1532.314276] BTRFS info (device loop2): disk space caching is enabled
kernel: [ 1532.314277] BTRFS info (device loop2): has skinny extents
kernel: [ 1532.314278] BTRFS info (device loop2): flagging fs with big metadata 
feature 
kernel: [ 1532.315442] BTRFS warning (device loop2): devid 2 uuid 
b6fe3a66-6a6d-42fe-9b57-5373a2f8d014 is missing
kernel: [ 1532.315882] BTRFS info (device loop2): checking UUID tree
kernel: [ 1532.319154] BTRFS error (device loop2): balance: invalid convert 
data profile single
systemd[965]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: 
Succeeded.
systemd[1]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: 
Succeeded.
kernel: [ 1532.524774] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic i686
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May  9 09:31 seq
 crw-rw 1 root audio 116, 33 May  9 09:31 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27
Architecture: i386
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 May  9 09:33:18 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R310
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 05XKKK
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R310
dmi.sys.vendor: Dell Inc.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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


** Tags: apport-bug disco i386 uec-im

[Kernel-packages] [Bug 1828380] Re: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on D i386

[Po-Hsu Lin]

Note that this issue does not exist on Disco AMD64 / ARM64 / PowerPC.
Just i386

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

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

Title:
  f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes
  failed on D i386

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

Bug description:
  Test failed with:
btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  
  Test log:
* Command: 
BINDIR=/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes 
/home

/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/ubuntu_btrfs_kerne
l_fixes.sh 
/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/fi
xes/f88ba6a2a44ee98e8d59654463dc157bb6d13c43.sh 2>&1
Exit status: 1
Duration: 11.0287649632

stdout:
Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

Btrfs: skip submitting barrier for missing device

I got an error on v3.13:
 BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO 
failure (errors while submitting device barriers.)

how to reproduce:
  > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
  > wipefs -a /dev/sdf2
  > mount -o degraded /dev/sdf1 /mnt
  > btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt

The reason of the error is that barrier_all_devices() failed to submit
barrier to the missing device.  However it is clear that we cannot do
anything on missing device, and also it is not necessary to care chunks
on the missing device.

This patch stops sending/waiting barrier if device is missing.

btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43

FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

  
  Syslog:
  kernel: [ 1531.598180] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  kernel: [ 1531.822544] BTRFS: device fsid 
28683721-4c7a-4922-a753-e61ca95c0726 devid 1 transid 5 /dev/loop2 
  kernel: [ 1531.917840] BTRFS: device fsid 
28683721-4c7a-4922-a753-e61ca95c0726 devid 2 transid 5 /dev/loop3 
  kernel: [ 1532.314274] BTRFS info (device loop2): allowing degraded mounts
  kernel: [ 1532.314276] BTRFS info (device loop2): disk space caching is 
enabled
  kernel: [ 1532.314277] BTRFS info (device loop2): has skinny extents
  kernel: [ 1532.314278] BTRFS info (device loop2): flagging fs with big 
metadata feature 
  kernel: [ 1532.315442] BTRFS warning (device loop2): devid 2 uuid 
b6fe3a66-6a6d-42fe-9b57-5373a2f8d014 is missing
  kernel: [ 1532.315882] BTRFS info (device loop2): checking UUID tree
  kernel: [ 1532.319154] BTRFS error (device loop2): balance: invalid convert 
data profile single
  systemd[965]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: 
Succeeded.
  systemd[1]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: 
Succeeded.
  kernel: [ 1532.524774] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 09:31 seq
   crw-rw 1 root audio 116, 33 May  9 09:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: i386
  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 May  9 09:33:18 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill: Error: [Errno 2] No such

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

[Ubuntu Kernel Bot]

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

apport-collect 1828380

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

Title:
  f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes
  failed on D i386

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

Bug description:
  Test failed with:
btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  
  Test log:
* Command: 
BINDIR=/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes 
/home

/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/ubuntu_btrfs_kerne
l_fixes.sh 
/home/ubuntu/autotest/client/tests/ubuntu_btrfs_kernel_fixes/fi
xes/f88ba6a2a44ee98e8d59654463dc157bb6d13c43.sh 2>&1
Exit status: 1
Duration: 11.0287649632

stdout:
Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

Btrfs: skip submitting barrier for missing device

I got an error on v3.13:
 BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO 
failure (errors while submitting device barriers.)

how to reproduce:
  > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
  > wipefs -a /dev/sdf2
  > mount -o degraded /dev/sdf1 /mnt
  > btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt

The reason of the error is that barrier_all_devices() failed to submit
barrier to the missing device.  However it is clear that we cannot do
anything on missing device, and also it is not necessary to care chunks
on the missing device.

This patch stops sending/waiting barrier if device is missing.

btrfs balance failed on /tmp/mnt-f88ba6a2a44ee98e8d59654463dc157bb6d13c43

FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

  
  Syslog:
  kernel: [ 1531.598180] Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
  kernel: [ 1531.822544] BTRFS: device fsid 
28683721-4c7a-4922-a753-e61ca95c0726 devid 1 transid 5 /dev/loop2 
  kernel: [ 1531.917840] BTRFS: device fsid 
28683721-4c7a-4922-a753-e61ca95c0726 devid 2 transid 5 /dev/loop3 
  kernel: [ 1532.314274] BTRFS info (device loop2): allowing degraded mounts
  kernel: [ 1532.314276] BTRFS info (device loop2): disk space caching is 
enabled
  kernel: [ 1532.314277] BTRFS info (device loop2): has skinny extents
  kernel: [ 1532.314278] BTRFS info (device loop2): flagging fs with big 
metadata feature 
  kernel: [ 1532.315442] BTRFS warning (device loop2): devid 2 uuid 
b6fe3a66-6a6d-42fe-9b57-5373a2f8d014 is missing
  kernel: [ 1532.315882] BTRFS info (device loop2): checking UUID tree
  kernel: [ 1532.319154] BTRFS error (device loop2): balance: invalid convert 
data profile single
  systemd[965]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: 
Succeeded.
  systemd[1]: tmp-mnt\x2df88ba6a2a44ee98e8d59654463dc157bb6d13c43.mount: 
Succeeded.
  kernel: [ 1532.524774] Test f88ba6a2a44ee98e8d59654463dc157bb6d13c43 returned 0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 09:31 seq
   crw-rw 1 root audio 116, 33 May  9 09:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: i386
  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 May  9 09:33:18 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEd

[Kernel-packages] [Bug 1802474] [NEW] test_map in ubuntu_bpf failed on 4.18 PowerPC

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The test_map test will fail with the following error on powerpc boxes:

$ sudo ./test_maps 
libbpf: object file doesn't contain bpf program
Failed to load SK_SKB parse prog

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12
Uname: Linux 4.18.0-11-generic ppc64le
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
Date: Fri Nov  9 08:37:46 2018
ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   8388544 0   -2
ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 
12:58:39 UTC 2018
SourcePackage: linux-signed-hwe-edge
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_dscr: DSCR is 0
cpu_freq:
 min:   3.694 GHz (cpu 159)
 max:   3.695 GHz (cpu 1)
 avg:   3.694 GHz
cpu_runmode:
 Could not retrieve current diagnostics mode,
 No kernel interface to firmware
cpu_smt: SMT=8

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug bionic cosmic package-from-proposed ppc64el uec-images
-- 
test_map in ubuntu_bpf failed on 4.18 PowerPC
https://bugs.launchpad.net/bugs/1802474
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 1826848] [NEW] ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0 kernel

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Test failed becuase:
   ./ip_defrag: sendto overlap: 1400: Operation not permitted


 selftests: net: ip_defrag.sh
 
 ipv6 tx:17 gso:1 (fail)
 OK
 ipv4 defrag
 PASS
 seed = 1556203721
 ipv4 defrag with overlaps
 PASS
 seed = 1556203722
 ipv6 defrag
 seed = 1556203756
 PASS
 ipv6 defrag with overlaps
 seed = 1556203756
 ./ip_defrag: sendto overlap: 1400: Operation not permitted
 not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

-- 
ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0 kernel
https://bugs.launchpad.net/bugs/1826848
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 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Ready for Testing
  phase-changed: Thursday, 09. May 2019 09:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   verification-testing: Pending -- Ready

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Ready for Testing
  phase-changed: Thursday, 09. May 2019 09:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic

[Po-Hsu Lin]

This issue does not exist on Disco.

Also, for the test result in the recent cycle, it has passed with Cosmic
AMD64 (node "daedalus"), but failed with i386 (node "pepe") and PowerPC
(P8 node "modoc" and P9 node "baltar")

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

Title:
  ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes
  generate kernel traces on Cosmic

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

Bug description:
  This issue can only be reproduced on certain HW, node "daedalus"
  (AMD64), "modoc" P8

  And this can only be reproduced when running the whole test suite, it
  will be fine if you just run this test:

Invoking test ff76b0565523319d7c1c0b51d5a5a8915d33efab

fix ff76b0565523319d7c1c0b51d5a5a8915d33efab

Btrfs: Don't allocate inode that is already in use

Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.

The same inode number is assigned twice, the second time this
leads to an EEXIST in btrfs_insert_empty_items().

Create subvolume '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s1' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2'
Create a snapshot of '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s2' 
in '/tmp/mnt-ff76b0565523319d7c1c0b51d5a5a8915d33efab/s3'

Found kernel issue:

[ 2713.591492] WARNING: CPU: 18 PID: 61234 at fs/btrfs/inode.c:9256 
btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591494] Modules linked in: btrfs zstd_compress nls_iso8859_1 
ipmi_ssif intel_rapl skx_edac nfit x86_pkg_temp_thermal intel_powerclamp joydev 
input_leds coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_rapl_perf mei_me mei ioatdma ipmi_si dca 
ipmi_devintf ipmi_msghandler acpi_pad acpi_power_meter mac_hid sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm hid_generic 
drm_kms_helper aesni_intel aes_x86_64 syscopyarea usbhid sysfillrect 
crypto_simd hid sysimgblt cryptd fb_sys_fops ahci glue_helper i40e drm lpc_ich 
libahci wmi [last unloaded: zstd_compress]
[ 2713.591577] CPU: 18 PID: 61234 Comm: umount Tainted: GW 
4.18.0-14-generic #15-Ubuntu
[ 2713.591579] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.01.00.0412.020920172159 02/09/2017
[ 2713.591611] RIP: 0010:btrfs_destroy_inode+0x1d7/0x210 [btrfs]
[ 2713.591612] Code: d0 31 d2 48 89 83 e0 fe ff ff 49 8b 85 e0 03 00 00 48 
85 c0 0f 94 c2 e9 4c ff ff ff 0f 0b e9 60 fe ff ff 0f 0b e9 67 fe ff ff <0f> 0b 
e9 6e fe ff ff 0f 0b e9 75 fe ff ff 0f 0b e9 7c fe ff ff 0f 
[ 2713.591666] RSP: 0018:a966b0bbfc48 EFLAGS: 00010206
[ 2713.591669] RAX: 90c5bf3e6800 RBX: 90c5e06bbc30 RCX: 

[ 2713.591671] RDX:  RSI:  RDI: 
90c5e06bbc30
[ 2713.591673] RBP: a966b0bbfc78 R08: 0001 R09: 
c08fe101
[ 2713.591674] R10: 90c58aac2510 R11: 0001 R12: 
90c5e06bbcb8
[ 2713.591676] R13: c0972940 R14: 90c5e06bbd88 R15: 
a966b0bbfd48
[ 2713.591679] FS:  7f31837e8080() GS:90c61fa8() 
knlGS:
[ 2713.591681] CS:  0010 DS:  ES:  CR0: 80050033
[ 2713.591682] CR2: 7f3183b70308 CR3: 00080167a002 CR4: 
007606e0
[ 2713.591685] DR0:  DR1:  DR2: 

[ 2713.591686] DR3:  DR6: fffe0ff0 DR7: 
0400
[ 2713.591688] PKRU: 5554
[ 2713.591689] Call Trace:
[ 2713.591702]  destroy_inode+0x3e/0x60
[ 2713.591707]  evict+0x139/0x1a0
[ 2713.591711]  iput+0x148/0x210
[ 2713.591739]  free_fs_root+0x1b/0xc0 [btrfs]
[ 2713.591766]  btrfs_drop_and_free_fs_root+0x7c/0xf0 [btrfs]
[ 2713.591793]  btrfs_free_fs_roots+0xdc/0x170 [btrfs]
[ 2713.591824]  ? __btrfs_sysfs_remove_fsid+0x68/0x70 [btrfs]
[ 2713.591852]  close_ctree+0x10c/0x2d0 [btrfs]
[ 2713.591872]  btrfs_put_super+0x15/0x20 [btrfs]
[ 2713.591878]  generic_shutdown_super+0x72/0x110
[ 2713.591882]  kill_anon_super+0x12/0x20
[ 2713.591904]  btrfs_kill_super+0x18/0x110 [btrfs]
[ 2713.591906]  deactivate_locked_super+0x3a/0x80
[ 2713.591907]  deactivate_super+0x51/0x60
[ 2713.591909]  cleanup_mnt+0x3f/0x70
[ 2713.591910]  __cleanup_mnt+0x12/0x20
[ 2713.591915]  task_work_run+0x9d/0xc0

[Kernel-packages] [Bug 1802474] Re: test_map in ubuntu_bpf failed on 4.18 PowerPC

[Po-Hsu Lin]

** Package changed: linux-signed-hwe-edge (Ubuntu) => linux (Ubuntu)

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

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

** Tags added: disco

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

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

Title:
  test_map in ubuntu_bpf failed on 4.18 PowerPC

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

Bug description:
  The test_map test will fail with the following error on powerpc boxes:

  $ sudo ./test_maps 
  libbpf: object file doesn't contain bpf program
  Failed to load SK_SKB parse prog

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12
  Uname: Linux 4.18.0-11-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  Date: Fri Nov  9 08:37:46 2018
  ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 
12:58:39 UTC 2018
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 159)
   max: 3.695 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

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

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

[Kernel-packages] [Bug 1819413] Re: [ICL] S0ix Enabling

[Anthony Wong]

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

** Changed in: linux-oem-osp1 (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
  [ICL] S0ix Enabling

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  New

Bug description:
  Description:

  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.

  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;

  (2) by runtime PM, i.e no system activities with display off.

  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.

   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine

  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM

  Both paths will require intel_idle driver support for S0ix support.

  238f9c11351f8af8534ae0318b4d9acc77b09ee8

  8aba056a4ea6da18186025a335a96b2f071e69d3

  6769fdbe27d782dfee5e459e25b44baacc7c8459

  cfb55af9add9c19806300fdb31f4cd25e67c6d1a

  4a5861f714293767980e4948c9a7c9e5e09c9b94

  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b

  cd89e92b7399a69512b8d855a2dd145c47399bf8

  d6827015e671cd17871c9b7a0fabe06c044f7470

  0e68eeea9894feeba2edf7ec63e4551b87f39621

  e50af8332785355de3cb40d9f5e8c45dbfc86f53

  Target Kernel: 5.1
  Target Release: 19.10

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

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

[Kernel-packages] [Bug 1827750] Re: Not boot with EFI

[Alex Smith]

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

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

Title:
  Not boot with EFI

Status in linux-raspi2 package in Ubuntu:
  Fix Committed

Bug description:
  Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. 
Please add support kernel option CONFIG_U(EFI)_STUB=y as default.
  Thanks.

  os: ubuntu 18.04 lts arm64
  hw: raspberry pi 3b (+ tiano core uefi)

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

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

[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0 kernel

[Po-Hsu Lin]

** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu)

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

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0
  kernel

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

Bug description:
  Test failed becuase:
 ./ip_defrag: sendto overlap: 1400: Operation not permitted

  
   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

[Kernel-packages] [Bug 1813136] Re: dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests failed with Power9 on Bionic

[Po-Hsu Lin]

Test passed on 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/1813136

Title:
  dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests  failed
  with Power9 on B/C/D

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

Bug description:
  This issue can be found on Power9 with Bionic / Cosmic kernel

  $ sudo ./dscr_sysfs_test
  test: dscr_sysfs_test
  tags: git_version:c186097-dirty
  !! killing dscr_sysfs_test
  !! child died by signal 15
  failure: dscr_sysfs_test

  Passed on Power8

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 07:22 seq
   crw-rw 1 root audio 116, 33 Jan 24 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  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:
  Date: Thu Jan 24 09:29:00 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. 
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd 
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.26 0.07 0.11 3/1363 35034
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 3482 00:17:520 0 EOF
   2: POSIX  ADVISORY  WRITE 3746 00:17:580 0 EOF
   3: POSIX  ADVISORY  WRITE 1800 00:17:368 0 EOF
   4: FLOCK  ADVISORY  WRITE 3744 00:17:568 0 EOF
   5: POSIX  ADVISORY  WRITE 3831 00:17:588 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 
2019
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 5
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 3)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

[Kernel-packages] [Bug 1813136] Re: dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests failed with Power9 on Bionic

[Po-Hsu Lin]

Correction: this test can be found failed with Disco with Power9 (ok
with P8)

** Tags added: disco

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

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

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

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

** Summary changed:

- dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests  failed with 
Power9 on Bionic
+ dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests  failed with 
Power9 on B/C/D

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

Title:
  dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests  failed
  with Power9 on B/C/D

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

Bug description:
  This issue can be found on Power9 with Bionic / Cosmic kernel

  $ sudo ./dscr_sysfs_test
  test: dscr_sysfs_test
  tags: git_version:c186097-dirty
  !! killing dscr_sysfs_test
  !! child died by signal 15
  failure: dscr_sysfs_test

  Passed on Power8

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 07:22 seq
   crw-rw 1 root audio 116, 33 Jan 24 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  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:
  Date: Thu Jan 24 09:29:00 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. 
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd 
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.26 0.07 0.11 3/1363 35034
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 3482 00:17:520 0 EOF
   2: POSIX  ADVISORY  WRITE 3746 00:17:580 0 EOF
   3: POSIX  ADVISORY  WRITE 1800 00:17:368 0 EOF
   4: FLOCK  ADVISORY  WRITE 3744 00:17:568 0 EOF
   5: POSIX  ADVISORY  WRITE 3831 00:17:588 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 
2019
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 5
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 3)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1826848

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 Disco)
   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/1826848

Title:
  ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0.0
  kernel

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

Bug description:
  Test failed becuase:
 ./ip_defrag: sendto overlap: 1400: Operation not permitted

  
   selftests: net: ip_defrag.sh
   
   ipv6 tx:17 gso:1 (fail)
   OK
   ipv4 defrag
   PASS
   seed = 1556203721
   ipv4 defrag with overlaps
   PASS
   seed = 1556203722
   ipv6 defrag
   seed = 1556203756
   PASS
   ipv6 defrag with overlaps
   seed = 1556203756
   ./ip_defrag: sendto overlap: 1400: Operation not permitted
   not ok 1..17 selftests: net: ip_defrag.sh [FAIL]

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1802474

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

Title:
  test_map in ubuntu_bpf failed on 4.18 PowerPC

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

Bug description:
  The test_map test will fail with the following error on powerpc boxes:

  $ sudo ./test_maps 
  libbpf: object file doesn't contain bpf program
  Failed to load SK_SKB parse prog

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12
  Uname: Linux 4.18.0-11-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  Date: Fri Nov  9 08:37:46 2018
  ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 
12:58:39 UTC 2018
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 159)
   max: 3.695 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

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

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

[Kernel-packages] [Bug 1801033] Re: test_verifier in ubuntu_bpf test failed with "Failed to load prog" on Cosmic s390x

[Po-Hsu Lin]

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

** Summary changed:

- test_verifier in ubuntu_bpf test failed with "Failed to load prog" on Cosmic 
s390x
+ test_verifier in ubuntu_bpf test failed with "Failed to load prog" on C/D 
s390x

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

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

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

Title:
  test_verifier in ubuntu_bpf test failed with "Failed to load prog" on
  C/D s390x

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

Bug description:
  There are 29 failures reported by the ubuntu_bpf test on Cosmic s390x
  KVM / Ubuntu on LPAR

  Failed test cases:

  #200/p runtime/jit: pass > 32bit index to tail_call FAIL retval 2 != 42
  [stdout] 0: (18) r3 = 0x1
  [stdout] 2: (18) r2 = 0x3a9cdc000
  [stdout] 4: (85) call bpf_tail_call#12
  [stdout] 5: (b7) r0 = 2
  [stdout] 6: (95) exit
  [stdout] processed 5 insns (limit 131072), stack depth 0

  #540/p calls: basic sanity FAIL
  [stdout] Failed to load prog 'Unknown error 524'!
  [stdout] 0: (85) call pc+2
  [stdout] caller:
  [stdout]  R10=fp0,call_-1
  [stdout] callee:
  [stdout]  frame1: R1=ctx(id=0,off=0,imm=0) R10=fp0,call_0
  [stdout] 3: (b7) r0 = 2
  [stdout] 4: (95) exit
  [stdout] returning from callee:
  [stdout]  frame1: R0_w=inv2 R1=ctx(id=0,off=0,imm=0) R10=fp0,call_0
  [stdout] to caller at 1:
  [stdout]  R0_w=inv2 R10=fp0,call_-1
  [stdout]
  [stdout] from 4 to 1: R0=inv2 R10=fp0,call_-1
  [stdout] 1: (b7) r0 = 1
  [stdout] 2: (95) exit
  [stdout] processed 5 insns (limit 131072), stack depth 0+0
  [stdout] JIT doesn't support bpf-to-bpf calls

  #541/p calls: not on unpriviledged FAIL
  (identical error message with #540/p)

  #542/p calls: div by 0 in subprog FAIL
  [stdout] Failed to load prog 'Unknown error 524'!
  [stdout] 0: (bf) r6 = r1
  [stdout] 1: (85) call pc+8
  [stdout] caller:
  [stdout]  R6=ctx(id=0,off=0,imm=0) R10=fp0,call_-1
  [stdout] callee:
  [stdout]  frame1: R1=ctx(id=0,off=0,imm=0) R10=fp0,call_1
  [stdout] 10: (b4) (u32) r2 = (u32) 0
  [stdout] 11: (b4) (u32) r3 = (u32) 1
  [stdout] 12: (3c) (u32) r3 /= (u32) r2
  [stdout] 13: (61) r0 = *(u32 *)(r1 +76)
  [stdout] 14: (95) exit
  [stdout] returning from callee:
  [stdout]  frame1: R0_w=pkt(id=0,off=0,r=0,imm=0) R1=ctx(id=0,off=0,imm=0) 
R2_w=inv0 R3_w=inv(id=0,umax_value=4294967295,var_off=(0x0; 0x)) 
R10=fp0,call_1
  [stdout] to caller at 2:
  [stdout]  R0_w=pkt(id=0,off=0,r=0,imm=0) R6=ctx(id=0,off=0,imm=0) 
R10=fp0,call_-1
  [stdout]
  [stdout] from 14 to 2: R0=pkt(id=0,off=0,r=0,imm=0) R6=ctx(id=0,off=0,imm=0) 
R10=fp0,call_-1
  [stdout] 2: (bf) r1 = r6
  [stdout] 3: (61) r1 = *(u32 *)(r1 +80)
  [stdout] 4: (bf) r2 = r0
  [stdout] 5: (07) r2 += 8
  [stdout] 6: (2d) if r2 > r1 goto pc+1
  [stdout]  R0=pkt(id=0,off=0,r=8,imm=0) R1=pkt_end(id=0,off=0,imm=0) 
R2=pkt(id=0,off=8,r=8,imm=0) R6=ctx(id=0,off=0,imm=0) R10=fp0,call_-1
  [stdout] 7: (71) r0 = *(u8 *)(r0 +0)
  [stdout] 8: (b7) r0 = 1
  [stdout] 9: (95) exit

  #551/p calls: conditional call 2 FAIL
  (error message has been clipped for this and the following tests, please 
refer to the complete test report link below)

  #553/p calls: conditional call 4 FAIL
  #556/p calls: using r0 returned by callee FAIL
  #558/p calls: callee is using r1 FAIL
  #559/p calls: callee using args1 FAIL
  #561/p calls: callee using two args FAIL
  #563/p calls: two calls with args FAIL
  #564/p calls: calls with stack arith FAIL
  #581/p calls: two calls with stack read FAIL
  #582/p calls: two calls with stack write FAIL
  #585/p calls: stack depth check using three frames. test1 FAIL
  #586/p calls: stack depth check using three frames. test2 FAIL
  #591/p calls: write into caller stack frame FAIL
  #593/p calls: two calls with stack write and void return FAIL
  #595/p calls: two calls that return map_value FAIL
  #596/p calls: two calls that return map_value with bool condition FAIL
  #599/p calls: two calls that receive map_value via arg=ptr_stack_of_caller. 
test2 FAIL
  #601/p calls: two calls that receive map_value_ptr_or_null via arg. test1 FAIL
  #603/p calls: pkt_ptr spill into caller stack FAIL
  #605/p calls: pkt_ptr spill into caller stack 3 FAIL
  #606/p calls: pkt_ptr spill into caller stack 4 FAIL
  #610/p calls: pkt_ptr spill into caller stack 8 FAIL
  #612/p calls: caller stack init to zero or map_value_or_null FAIL
  #614/p calls: two calls returning different map pointers for lookup (hash, 
array) FAIL
  #639/p ld_abs: jump around ld_abs FAIL
  Summary: 869 PASSED, 0 SKIPPED, 29 FAIL

[Kernel-packages] [Bug 1827845] Re: ubuntu_bpf_jit report result in D on s390x is a bit confusing

[Po-Hsu Lin]

Issue could be found on KVM and LPAR.

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

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

Title:
  ubuntu_bpf_jit report result in D on s390x is a bit confusing

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

Bug description:
  The only failure is the test_bpf module load failure, and there are 378 tests 
(0-377)
  But the result shows "Summary: 377 PASSED, 1 FAILED"

  Module test_bpf load failure
  [  873.481738] test_bpf: #0 TAX jited:1 36 34 35 PASS
  [  873.481888] test_bpf: #1 TXA jited:1 17 17 17 PASS
  [  873.481960] test_bpf: #2 ADD_SUB_MUL_K jited:1 18 PASS
  [  873.481997] test_bpf: #3 DIV_MOD_KX jited:1 35 PASS
  [  873.482054] test_bpf: #4 AND_OR_LSH_K jited:1 16 16 PASS
  [  873.482106] test_bpf: #5 LD_IMM_0 jited:1 16 PASS
  [  873.482141] test_bpf: #6 LD_IND jited:1 48 47 47 PASS
  [  873.482305] test_bpf: #7 LD_ABS jited:1 49 49 49 PASS
  [  873.482472] test_bpf: #8 LD_ABS_LL jited:1 72 72 PASS
  [  873.482637] test_bpf: #9 LD_IND_LL jited:1 49 49 49 PASS
  [  873.482804] test_bpf: #10 LD_ABS_NET jited:1 71 71 PASS
  [  873.482966] test_bpf: #11 LD_IND_NET jited:1 48 48 48 PASS
  [  873.483132] test_bpf: #12 LD_PKTTYPE jited:1 18 18 PASS
  [  873.483189] test_bpf: #13 LD_MARK jited:1 18 18 PASS
  [  873.483242] test_bpf: #14 LD_RXHASH jited:1 18 18 PASS
  [  873.483295] test_bpf: #15 LD_QUEUE jited:1 18 18 PASS
  [  873.483347] test_bpf: #16 LD_PROTOCOL jited:1 20 20 PASS
  [  873.483410] test_bpf: #17 LD_VLAN_TAG jited:1 18 18 PASS
  [  873.483463] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 17 17 PASS
  [  873.483515] test_bpf: #19 LD_IFINDEX jited:1 17 17 PASS
  [  873.483567] test_bpf: #20 LD_HATYPE jited:1 17 17 PASS
  [  873.483618] test_bpf: #21 LD_CPU jited:1 52 52 PASS
  [  873.483742] test_bpf: #22 LD_NLATTR jited:1 34 44 PASS
  [  873.483839] test_bpf: #23 LD_NLATTR_NEST jited:1 155 236 PASS
  [  873.484254] test_bpf: #24 LD_PAYLOAD_OFF jited:1 295 325 PASS
  [  873.484894] test_bpf: #25 LD_ANC_XOR jited:1 16 16 PASS
  [  873.484945] test_bpf: #26 SPILL_FILL jited:1 20 20 20 PASS
  [  873.485026] test_bpf: #27 JEQ jited:1 47 18 18 PASS
  [  873.485131] test_bpf: #28 JGT jited:1 47 18 18 PASS
  [  873.485236] test_bpf: #29 JGE (jt 0), test 1 jited:1 46 18 18 PASS
  [  873.485339] test_bpf: #30 JGE (jt 0), test 2 jited:1 18 18 18 PASS
  [  873.485414] test_bpf: #31 JGE jited:1 34 35 35 PASS
  [  873.485540] test_bpf: #32 JSET jited:1 37 36 39 PASS
  [  873.485678] test_bpf: #33 tcpdump port 22 jited:1 47 52 57 PASS
  [  873.485871] test_bpf: #34 tcpdump complex jited:1 47 50 74 PASS
  [  873.486082] test_bpf: #35 RET_A jited:1 16 16 PASS
  [  873.486132] test_bpf: #36 INT: ADD trivial jited:1 16 PASS
  [  873.486165] test_bpf: #37 INT: MUL_X jited:1 16 PASS
  [  873.486197] test_bpf: #38 INT: MUL_X2 jited:1 17 PASS
  [  873.486230] test_bpf: #39 INT: MUL32_X jited:1 17 PASS
  [  873.486263] test_bpf: #40 INT: ADD 64-bit jited:1 36 PASS
  [  873.486331] test_bpf: #41 INT: ADD 32-bit jited:1 50 PASS
  [  873.486411] test_bpf: #42 INT: SUB jited:1 33 PASS
  [  873.486472] test_bpf: #43 INT: XOR jited:1 22 PASS
  [  873.486516] test_bpf: #44 INT: MUL jited:1 71 PASS
  [  873.486609] test_bpf: #45 MOV REG64 jited:1 19 PASS
  [  873.486647] test_bpf: #46 MOV REG32 jited:1 19 PASS
  [  873.486685] test_bpf: #47 LD IMM64 jited:1 20 PASS
  [  873.486725] test_bpf: #48 INT: ALU MIX jited:1 24 PASS
  [  873.486788] test_bpf: #49 INT: shifts by register jited:1 19 PASS
  [  873.486827] test_bpf: #50 check: missing ret PASS
  [  873.486834] test_bpf: #51 check: div_k_0 PASS
  [  873.486840] test_bpf: #52 check: unknown insn PASS
  [  873.486846] test_bpf: #53 check: out of range spill/fill PASS
  [  873.486851] test_bpf: #54 JUMPS + HOLES jited:1 21 PASS
  [  873.486964] test_bpf: #55 check: RET X PASS
  [  873.486970] test_bpf: #56 check: LDX + RET X PASS
  [  873.486976] test_bpf: #57 M[]: alt STX + LDX jited:1 57 PASS
  [  873.487065] test_bpf: #58 M[]: full STX + full LDX jited:1 27 PASS
  [  873.487122] test_bpf: #59 check: SKF_AD_MAX PASS
  [  873.487128] test_bpf: #60 LD [SKF_AD_OFF-1] jited:1 48 PASS
  [  873.487196] test_bpf: #61 load 64-bit immediate jited:1 17 PASS
  [  873.487231] test_bpf: #62 ALU_MOV_X: dst = 2 jited:1 16 PASS
  [  873.487265] test_bpf: #63 ALU_MOV_X: dst = 4294967295 jited:1 16 PASS
  [  873.487298] test_bpf: #64 ALU64_MOV_X: dst = 2 jited:1 16 PASS
  [  873.487331] test_bpf: #65 ALU64_MOV_X: dst = 4294967295 jited:1 16 PASS
  [  873.487364] test_bpf: #66 ALU_MOV_K: dst = 2 jited:1 16 PASS
  [  873.487397] test_bpf: #67 ALU_MOV_K: dst = 4294967295 jited:1 16 PASS
  [  873.487430] test_bpf: #68 ALU_MOV_K: 0x = 
0x jited:1 16 PASS
  [  873.4874

[Kernel-packages] [Bug 1826146] Re: linux-snapdragon: 5.0.0-1011.11 -proposed tracker

[Taihsiang Ho]

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

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

Title:
  linux-snapdragon: 5.0.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  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: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826139] Re: linux-raspi2: 5.0.0-1007.7 -proposed tracker

[Taihsiang Ho]

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

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

Title:
  linux-raspi2: 5.0.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  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: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 11:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826146] Re: linux-snapdragon: 5.0.0-1011.11 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-snapdragon: 5.0.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  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: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 10:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux: 5.0.0-14.15 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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 1826147 (bionic/linux-hwe-edge), bug 1827847 
(bionic/linux-oem-osp1)
  derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 
(linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 03. May 2019 08:01 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

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

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

[Kernel-packages] [Bug 1826139] Re: linux-raspi2: 5.0.0-1007.7 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 11:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-raspi2: 5.0.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  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: 1826150
  phase: Signoff
  phase-changed: Thursday, 02. May 2019 11:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/disco/5.0.0-14.15/disco-
proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1826150

Title:
  linux: 5.0.0-14.15 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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 1826147 (bionic/linux-hwe-edge), bug 1827847 
(bionic/linux-oem-osp1)
  derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 
(linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 03. May 2019 08:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1826147 (bionic/linux-hwe-edge), bug 1827847 
(bionic/linux-oem-osp1)
  derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 
(linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 03. May 2019 08:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

Title:
  linux: 5.0.0-14.15 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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 1826147 (bionic/linux-hwe-edge), bug 1827847 
(bionic/linux-oem-osp1)
  derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 
(linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 03. May 2019 08:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1826352] Re: linux-azure: 4.15.0-1044.48~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826354
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 09. May 2019 09:44 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 09. May 2019 10:58 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
+ sync

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

Title:
  linux-azure: 4.15.0-1044.48~14.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-signing-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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: 1826354
  phase: Promote to Proposed
  phase-changed: Thursday, 09. May 2019 10:58 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 09. May 2019 09:43 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 09. May 2019 11:04 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
+ sync

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: 1826036
  phase: Promote to Proposed
  phase-changed: Thursday, 09. May 2019 11:04 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync

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

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

[Kernel-packages] [Bug 1828394] [NEW] [UBUNTU] qdio: clear intparm during shutdown

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Description:   qdio: clear intparm during shutdown 
Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
   dereference in virtual kernel address space".
Problem:   During shutdown, qdio returns its ccw device back to control
   by qeth - but doesn't reset the interrupt parameter on the
   device. If qdio_shutdown() failed to terminate its
   long-running IO on the ccw_device, qeth will subsequently
   do so. In this case the IRQ for the IO completion is
   presented to qeth_irq() with the _old_ interrupt parameter,
   which gets mis-interpreted as a valid qeth_cmd_buffer
   pointer. Dereferencing this bogus pointer in
   qeth_release_buffer() triggers the crash.
Solution:  When returning the ccw device in qdio_shutdown(), also reset
   its interrupt parameter.
Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

Component: Kernel
Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

Reported:  Ubuntu 18.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-177513 severity-high 
targetmilestone-inin18041
-- 
[UBUNTU] qdio: clear intparm during shutdown
https://bugs.launchpad.net/bugs/1828394
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 1828391] [NEW] xfstests failed to build on Cosmic/Disco

[Po-Hsu Lin]

Public bug reported:

This issue was addressed before in bug 1802486

But it's failing again now, looks like something wrong in the upstream repo:
  ./configure: line 8704: test: $(SHELL): binary operator expected

Please find the attachment for the build log.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May  9 08:43 seq
 crw-rw 1 root audio 116, 33 May  9 08:43 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Thu May  9 11:05:42 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Cavium ThunderX CRB
PciMultimedia:

ProcFB:
 0 EFI VGA
 1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 0
dmi.chassis.vendor: Cavium
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
dmi.product.family: Default string
dmi.product.name: ThunderX CRB
dmi.product.sku: Default string
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Cavium

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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

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


** Tags: apport-bug arm64 disco uec-images

** Attachment added: "build.log"
   https://bugs.launchpad.net/bugs/1828391/+attachment/5262658/+files/build.log

** Summary changed:

- xfstests failed to build on Disco
+ xfstests failed to build on Cosmic/Disco

** Description changed:

  This issue was addressed before in bug 1802486
  
  But it's failing again now, looks like something wrong in the upstream repo:
-   ./configure: line 8704: test: $(SHELL): binary operator expected
- 
+   ./configure: line 8704: test: $(SHELL): binary operator expected
  
  Please find the attachment for the build log.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic aarch64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 May  9 08:43 seq
-  crw-rw 1 root audio 116, 33 May  9 08:43 timer
+  total 0
+  crw-rw 1 root audio 116,  1 May  9 08:43 seq
+  crw-rw 1 root audio 116, 33 May  9 08:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
-  
+ 
  Date: Thu May  9 11:05:42 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
-  
+ 
  ProcFB:
-  0 EFI VGA
-  1 astdrmfb
+  0 EFI VGA
+  1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-13-generic N/A
-  linux-backports-modules-5.0.0-13-generic  N/A
-  linux-firmware1.178
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To

[Kernel-packages] [Bug 1826336] Re: linux-oem: 4.15.0-1037.42 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/oem/4.15.0-1037.42/oem-4.15-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-oem: 4.15.0-1037.42 -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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1826358
  phase: Testing
  phase-changed: Friday, 03. May 2019 09:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1828394] [NEW] [UBUNTU] qdio: clear intparm during shutdown

[bugproxy]

Public bug reported:

Description:   qdio: clear intparm during shutdown 
Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
   dereference in virtual kernel address space".
Problem:   During shutdown, qdio returns its ccw device back to control
   by qeth - but doesn't reset the interrupt parameter on the
   device. If qdio_shutdown() failed to terminate its
   long-running IO on the ccw_device, qeth will subsequently
   do so. In this case the IRQ for the IO completion is
   presented to qeth_irq() with the _old_ interrupt parameter,
   which gets mis-interpreted as a valid qeth_cmd_buffer
   pointer. Dereferencing this bogus pointer in
   qeth_release_buffer() triggers the crash.
Solution:  When returning the ccw device in qdio_shutdown(), also reset
   its interrupt parameter.
Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

Component: Kernel
Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

Reported:  Ubuntu 18.04

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-177513 severity-high 
targetmilestone-inin18041

** Tags added: architecture-s39064 bugnameltc-177513 severity-high
targetmilestone-inin18041

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU] qdio: clear intparm during shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   qdio: clear intparm during shutdown 
  Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
 dereference in virtual kernel address space".
  Problem:   During shutdown, qdio returns its ccw device back to control
 by qeth - but doesn't reset the interrupt parameter on the
 device. If qdio_shutdown() failed to terminate its
 long-running IO on the ccw_device, qeth will subsequently
 do so. In this case the IRQ for the IO completion is
 presented to qeth_irq() with the _old_ interrupt parameter,
 which gets mis-interpreted as a valid qeth_cmd_buffer
 pointer. Dereferencing this bogus pointer in
 qeth_release_buffer() triggers the crash.
  Solution:  When returning the ccw device in qdio_shutdown(), also reset
 its interrupt parameter.
  Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

  Component: Kernel
  Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

  Reported:  Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1826335] Re: linux-snapdragon: 4.15.0-1052.56 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.15.0-1052.56/snapdragon-4.15-proposed-
published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-snapdragon: 4.15.0-1052.56 -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 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1826358
  phase: Testing
  phase-changed: Tuesday, 30. April 2019 12:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1828391

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 Cosmic)
   Status: New => Incomplete

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

Title:
  xfstests failed to build on Cosmic/Disco

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

Bug description:
  This issue was addressed before in bug 1802486

  But it's failing again now, looks like something wrong in the upstream repo:
    ./configure: line 8704: test: $(SHELL): binary operator expected

  Please find the attachment for the build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: User Name 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 08:43 seq
   crw-rw 1 root audio 116, 33 May  9 08:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Thu May  9 11:05:42 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: ThunderX CRB
  dmi.product.sku: Default string
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

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

[Po-Hsu Lin]

For Disco (no failure but reported 1 failed), please refer to bug
1827845

As it's different from this report, I will mark it as fix-released for
Disco here.

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

** Summary changed:

- Unable to insert test_bpf module for ubuntu_bpf_jit s390x
+ Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x

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

Title:
  Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X
  s390x

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1826336] Re: linux-oem: 4.15.0-1037.42 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

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

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

Title:
  linux-oem: 4.15.0-1037.42 -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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1826358
  phase: Signoff
  phase-changed: Thursday, 09. May 2019 11:39 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/1826336/+subscriptions

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

[Kernel-packages] [Bug 1826335] Re: linux-snapdragon: 4.15.0-1052.56 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826358
- phase: Testing
- phase-changed: Tuesday, 30. April 2019 12:39 UTC
+ phase: Signoff
+ phase-changed: Thursday, 09. May 2019 11:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-snapdragon: 4.15.0-1052.56 -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 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1826358
  phase: Signoff
  phase-changed: Thursday, 09. May 2019 11:39 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/1826335/+subscriptions

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2019-05-09 07:46 EDT---
Problem was detected on 16.04.5 but is the same kernel like 18.04.
Can a test kernel be provided for our test. That would be great..
Many thx in advance

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

Title:
  [UBUNTU] qdio: clear intparm during shutdown

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

Bug description:
  Description:   qdio: clear intparm during shutdown 
  Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
 dereference in virtual kernel address space".
  Problem:   During shutdown, qdio returns its ccw device back to control
 by qeth - but doesn't reset the interrupt parameter on the
 device. If qdio_shutdown() failed to terminate its
 long-running IO on the ccw_device, qeth will subsequently
 do so. In this case the IRQ for the IO completion is
 presented to qeth_irq() with the _old_ interrupt parameter,
 which gets mis-interpreted as a valid qeth_cmd_buffer
 pointer. Dereferencing this bogus pointer in
 qeth_release_buffer() triggers the crash.
  Solution:  When returning the ccw device in qdio_shutdown(), also reset
 its interrupt parameter.
  Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

  Component: Kernel
  Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

  Reported:  Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1828394] Re: [UBUNTU] qdio: clear intparm during shutdown

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

Title:
  [UBUNTU] qdio: clear intparm during shutdown

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

Bug description:
  Description:   qdio: clear intparm during shutdown 
  Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
 dereference in virtual kernel address space".
  Problem:   During shutdown, qdio returns its ccw device back to control
 by qeth - but doesn't reset the interrupt parameter on the
 device. If qdio_shutdown() failed to terminate its
 long-running IO on the ccw_device, qeth will subsequently
 do so. In this case the IRQ for the IO completion is
 presented to qeth_irq() with the _old_ interrupt parameter,
 which gets mis-interpreted as a valid qeth_cmd_buffer
 pointer. Dereferencing this bogus pointer in
 qeth_release_buffer() triggers the crash.
  Solution:  When returning the ccw device in qdio_shutdown(), also reset
 its interrupt parameter.
  Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

  Component: Kernel
  Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

  Reported:  Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1828394] Re: [UBUNTU] qdio: clear intparm during shutdown

[Frank Heimes]

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [UBUNTU] qdio: clear intparm during shutdown

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

Bug description:
  Description:   qdio: clear intparm during shutdown 
  Symptom:   Crash in qeth_irq() with "Unable to handle kernel pointer
 dereference in virtual kernel address space".
  Problem:   During shutdown, qdio returns its ccw device back to control
 by qeth - but doesn't reset the interrupt parameter on the
 device. If qdio_shutdown() failed to terminate its
 long-running IO on the ccw_device, qeth will subsequently
 do so. In this case the IRQ for the IO completion is
 presented to qeth_irq() with the _old_ interrupt parameter,
 which gets mis-interpreted as a valid qeth_cmd_buffer
 pointer. Dereferencing this bogus pointer in
 qeth_release_buffer() triggers the crash.
  Solution:  When returning the ccw device in qdio_shutdown(), also reset
 its interrupt parameter.
  Reproduction:  Offline an OSA CHPID with multiple active qeth interfaces.

  Component: Kernel
  Upstream-ID:   89286320a236d245834075fa13adb0bdd827ecaa

  Reported:  Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1828351] Re: RAID 10 with MegaRaid controller gives poor write performance

[Nicolas Pochet]

Unsubscribing field-critical and marking as invalid. The main reason of
this was that bcache was not tuned automatically.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1828351

Title:
  RAID 10 with MegaRaid controller gives poor write performance

Status in linux package in Ubuntu:
  Invalid

Bug description:
  On a Bionic server (Cisco UCS C240 M5) with a MegaRaid controller (Cisco 12G 
Modular Raid Controller UCSC-RAID-M5), I can observe very slow writes on the 
RAID 10 device that was created.
  A simple test:
  dd if=/dev/zero of=out bs=1M count=100
  Outputs a 35MB/s speed.

  The RAID 10 is composed of 4 HDDs (TOSH MG04SCA60EA T0A0CAF8YC 6TB) was 
configured with the default settings [0]:
  Strip size: 64K
  Access Policy: RW
  Read Policy: Normal
  Write Policy: Writethrough
  IO Policy: Direct
  Disable BGI: No

  uname -a
  4.15.0-48-generic #51-Ubuntu SMP

  [0]
  
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/raid/configuration/guide/RAID_GUIDE/MegaRAID.html

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

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

** Changed in: kernel-sru-workflow/verification-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: 1826036
- phase: Promote to Proposed
- phase-changed: Thursday, 09. May 2019 11:04 UTC
+ phase: Signoff
+ phase-changed: Thursday, 09. May 2019 12:34 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Pending -- Ready

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  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:
  Fix Released
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: 1826036
  phase: Signoff
  phase-changed: Thursday, 09. May 2019 12:34 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: Pending -- Ready

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

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

[Kernel-packages] [Bug 1826339] Re: linux-gcp: 4.15.0-1031.33~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1827360 (linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826340
  phase: Signoff
  phase-changed: Wednesday, 01. May 2019 10:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Pending -- nvidia GCP object not found -- 
current-driver-4.15.0-1031-gcp-amd64
+   promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1031-gcp-amd64
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1031.33~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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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

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

  derivatives: bug 1827360 (linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826340
  phase: Signoff
  phase-changed: Wednesday, 01. May 2019 10:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1031-gcp-amd64
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/1826339/+subscriptions

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

[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

[Hui Wang]

After booting up, please run:

ls -la /dev/snd/   #could you see some dev nodes

aplay -l  # could you see some audio devices

sudo chmod a+rw /dev/snd/*
aplay -l # could you see some different output from the 1st time.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  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-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions

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

[Kernel-packages] [Bug 1826352] Re: linux-azure: 4.15.0-1044.48~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

** 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: 1826354
- phase: Promote to Proposed
- phase-changed: Thursday, 09. May 2019 10:58 UTC
+ phase: Signoff
+ phase-changed: Thursday, 09. May 2019 12:46 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   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/1826352

Title:
  linux-azure: 4.15.0-1044.48~14.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-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826354
  phase: Signoff
  phase-changed: Thursday, 09. May 2019 12:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1828410] [NEW] Disco update: 5.0.7 upstream stable release

[Kleber Sacilotto de Souza]

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:

   5.0.7 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Disco update: 5.0.7 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 5.0.7 upstream stable release
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1826034] Re: linux-aws: 4.4.0-1043.46 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1826036
  phase: Signoff
  phase-changed: Thursday, 09. May 2019 12:34 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: Pending -- Ready

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  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:
  Fix Released
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: 1826036
  phase: Signoff
  phase-changed: Thursday, 09. May 2019 12:34 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

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

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

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

[bugproxy]

--- Comment From klaus.theur...@de.ibm.com 2019-05-09 08:59 EDT---
ok, I go the image with 18.04 and could recreate the problem.
Then I installed all packages with apt install ./package-name and did a reboot 
to activate the new kernel.
Questions:
- perf (binary) is no longer available via PATH after package install. Did the 
package install of linux-tools-common remove perf?

with
dpkg -c linux-tools-common_4.15.0-49.53+lp1828166_all.deb
drwxr-xr-x root/root 0 2019-05-08 16:19 ./
drwxr-xr-x root/root 0 2019-05-08 16:19 ./usr/
drwxr-xr-x root/root 0 2019-05-08 16:19 ./usr/share/
drwxr-xr-x root/root 0 2019-05-08 16:19 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-05-08 16:19 
./usr/share/doc/linux-tools-common/
-rw-r--r-- root/root194820 2019-05-08 16:17 
./usr/share/doc/linux-tools-common/changelog.Debian.gz
-rw-r--r-- root/root  1292 2019-05-08 16:17 
./usr/share/doc/linux-tools-common/copyright

Should perf be included here?

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

Title:
  perf top problem on z with Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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

[Kernel-packages] [Bug 1828415] [NEW] Disco update: 5.0.8 upstream stable release

[Kleber Sacilotto de Souza]

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:

   5.0.8 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Disco update: 5.0.8 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 5.0.8 upstream stable release
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1828410] Re: Disco update: 5.0.7 upstream stable release

[Kleber Sacilotto de Souza]

The following patches have been skipped as they have already been
applied:

d8dbb581d4f86a2ac669c056fc71a28ebeb367f4 - apparmor: fix double free when 
unpack of secmark rules fails
efdcad62e7b8a02f5ccca57806dce1482ac8 - scsi: hisi_sas: Set PHY linkrate 
when disconnected
4790595723d4b833b18c994973d39f9efb842887 - scsi: hisi_sas: Fix a timeout race 
of driver internal and SMP IO
eb4c2ccbad6c688be791e0c08640a40124558c03 - net: hns3: fix setting of the hns 
reset_type for rdma hw errors
4e46c2a956215482418d7b315749fb1b6c6bc224 - efi/arm/arm64: Allow 
SetVirtualAddressMap() to be omitted


** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    5.0.7 upstream stable release
+    from git://git.kernel.org/
  
-5.0.7 upstream stable release
-from git://git.kernel.org/
+ The following patches were applied:
+ * ext4: cleanup bh release code in ext4_ind_remove_space()
+ * CIFS: fix POSIX lock leak and invalid ptr deref
+ * nvme-fc: fix numa_node when dev is null
+ * nvme-loop: init nvmet_ctrl fatal_err_work when allocate
+ * h8300: use cc-cross-prefix instead of hardcoding h8300-unknown-linux-
+ * f2fs: fix to adapt small inline xattr space in __find_inline_xattr()
+ * f2fs: fix to avoid deadlock in f2fs_read_inline_dir()
+ * tracing: kdb: Fix ftdump to not sleep
+ * net/mlx5e: Fix access to non-existing receive queue
+ * net/mlx5: Avoid panic when setting vport rate
+ * net/mlx5: Avoid panic when setting vport mac, getting vport config
+ * xsk: fix to reject invalid flags in xsk_bind
+ * clk: ti: clkctrl: Fix clkdm_name regression for TI_CLK_CLKCTRL_COMPAT
+ * gpio: gpio-omap: fix level interrupt idling
+ * include/linux/relay.h: fix percpu annotation in struct rchan
+ * sysctl: handle overflow for file-max
+ * net: stmmac: Avoid sometimes uninitialized Clang warnings
+ * enic: fix build warning without CONFIG_CPUMASK_OFFSTACK
+ * libbpf: force fixdep compilation at the start of the build
+ * iio: adc: fix warning in Qualcomm PM8xxx HK/XOADC driver
+ * x86/hyperv: Fix kernel panic when kexec on HyperV
+ * perf c2c: Fix c2c report for empty numa node
+ * mm/sparse: fix a bad comparison
+ * mm/cma.c: cma_declare_contiguous: correct err handling
+ * mm/page_ext.c: fix an imbalance with kmemleak
+ * mm, swap: bounds check swap_info array accesses to avoid NULL derefs
+ * docs/core-api/mm: fix user memory accessors formatting
+ * mm,oom: don't kill global init via memory.oom.group
+ * memcg: killed threads should not invoke memcg OOM killer
+ * mm, mempolicy: fix uninit memory access
+ * mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512!
+ * mm/slab.c: kmemleak no scan alien caches
+ * ocfs2: fix a panic problem caused by o2cb_ctl
+ * f2fs: do not use mutex lock in atomic context
+ * f2fs: fix to data block override node segment by mistake
+ * fs/file.c: initialize init_files.resize_wait
+ * page_poison: play nicely with KASAN
+ * kasan: fix kasan_check_read/write definitions
+ * cifs: use correct format characters
+ * dm thin: add sanity checks to thin-pool and external snapshot creation
+ * f2fs: fix to check inline_xattr_size boundary correctly
+ * cifs: Accept validate negotiate if server return NT_STATUS_NOT_SUPPORTED
+ * cifs: Fix NULL pointer dereference of devname
+ * perf beauty msg_flags: Add missing %s lost when adding prefix suppression 
logic
+ * netfilter: nf_tables: check the result of dereferencing base_chain->stats
+ * PCI: mediatek: Fix memory mapped IO range size computation
+ * netfilter: conntrack: tcp: only close if RST matches exact sequence
+ * iommu/vt-d: Disable ATS support on untrusted devices
+ * jbd2: fix invalid descriptor block checksum
+ * ext4: fix bigalloc cluster freeing when hole punching under load
+ * fs: fix guard_bio_eod to check for real EOD errors
+ * tools lib traceevent: Fix buffer overflow in arg_eval
+ * mm/resource: Return real error codes from walk failures
+ * PCI/PME: Fix hotplug/sysfs remove deadlock in pcie_pme_remove()
+ * wil6210: check null pointer in _wil_cfg80211_merge_extra_ies
+ * mt76: fix a leaked reference by adding a missing of_node_put
+ * a

[Kernel-packages] [Bug 1828415] Re: Disco update: 5.0.8 upstream stable release

[Kleber Sacilotto de Souza]

The following patches have been skipped as they have already been
applied:

f28cd2af22a0c134e4aa1c64a70f70d815d473fb - openvswitch: fix flow actions 
reallocation
cae30527901d9590db0e12ace994c1d58bea87fd - ALSA: hda - Add two more machines to 
the power_save_blacklist
21635d7311734d2d1b177f8a95e2f9386174b76d - drm/i915/dp: revert back to max link 
rate and lane count on eDP
5a3ae7b314a2259b1188b22b392f5eba01e443ee - arm64/ftrace: fix inadvertent BUG() 
in trampoline check
acff78477b9b4f26ecdf65733a4ed77fe837e9dc - KVM: x86: nVMX: close leak of L0's 
x2APIC MSRs (CVE-2019-3887)
c73f4c998e1fd4249b9edfa39e23f4fda2b9b041 - KVM: x86: nVMX: fix x2APIC VTPR read 
intercept


** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    5.0.8 upstream stable release
+    from git://git.kernel.org/
  
-5.0.8 upstream stable release
-from git://git.kernel.org/
+ The following patches were applied:
+ * drm/i915/gvt: do not let pin count of shadow mm go negative
+ * kbuild: pkg: use -f $(srctree)/Makefile to recurse to top Makefile
+ * netfilter: nft_compat: use .release_ops and remove list of extension
+ * netfilter: nf_tables: use-after-free in dynamic operations
+ * netfilter: nf_tables: add missing ->release_ops() in error path of newrule()
+ * hv_netvsc: Fix unwanted wakeup after tx_disable
+ * ibmvnic: Fix completion structure initialization
+ * ip6_tunnel: Match to ARPHRD_TUNNEL6 for dev type
+ * ipv6: Fix dangling pointer when ipv6 fragment
+ * ipv6: sit: reset ip header pointer in ipip6_rcv
+ * kcm: switch order of device registration to fix a crash
+ * net: ethtool: not call vzalloc for zero sized memory request
+ * net-gro: Fix GRO flush when receiving a GSO packet.
+ * net/mlx5: Decrease default mr cache size
+ * netns: provide pure entropy for net_hash_mix()
+ * net: rds: force to destroy connection if t_sock is NULL in 
rds_tcp_kill_sock().
+ * net/sched: act_sample: fix divide by zero in the traffic path
+ * net/sched: fix ->get helper of the matchall cls
+ * qmi_wwan: add Olicard 600
+ * r8169: disable ASPM again
+ * sctp: initialize _pad of sockaddr_in before copying to user memory
+ * tcp: Ensure DCTCP reacts to losses
+ * tcp: fix a potential NULL pointer dereference in tcp_sk_exit
+ * vrf: check accept_source_route on the original netdevice
+ * net/mlx5e: Fix error handling when refreshing TIRs
+ * net/mlx5e: Add a lock on tir list
+ * nfp: validate the return code from dev_queue_xmit()
+ * nfp: disable netpoll on representors
+ * bnxt_en: Improve RX consumer index validity check.
+ * bnxt_en: Reset device on RX buffer errors.
+ * net: ip_gre: fix possible use-after-free in erspan_rcv
+ * net: ip6_gre: fix possible use-after-free in ip6erspan_rcv
+ * net: bridge: always clear mcast matching struct on reports and leaves
+ * net: thunderx: fix NULL pointer dereference in nicvf_open/nicvf_stop
+ * net: vrf: Fix ping failed when vrf mtu is set to 0
+ * net: core: netif_receive_skb_list: unlist skb before passing to pt->func
+ * r8169: disable default rx interrupt coalescing on RTL8168
+ * net: mlx5: Add a missing check on idr_find, free buf
+ * net/mlx5e: Update xoff formula
+ * net/mlx5e: Update xon formula
+ * kbuild: clang: choose GCC_TOOLCHAIN_DIR not on LD
+ * lib/string.c: implement a basic bcmp
+ * Revert "clk: meson: clean-up clock registration"
+ * tty: mark Siemens R3964 line discipline as BROKEN
+ * tty: ldisc: add sysctl to prevent autoloading of ldiscs
+ * hwmon: (w83773g) Select REGMAP_I2C to fix build error
+ * hwmon: (occ) Fix power sensor indexing
+ * SMB3: Allow persistent handle timeout to be configurable on mount
+ * HID: logitech: Handle 0 scroll events for the m560
+ * ACPICA: Clear status of GPEs before enabling them
+ * ACPICA: Namespace: remove address node from global list after method 
termination
+ * ALSA: seq: Fix OOB-reads from strlcpy
+ * ALSA: hda/realtek: Enable headset MIC of Acer TravelMate B114-21 with ALC233
+ * ALSA: hda/realtek - Add quirk for Tuxedo XC 1509
+ * ALSA: xen-front: Do not use stream buffer size before it is set
+ * mm/huge_memory.c: fix modifyi

[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04

[Frank Heimes]

Hi, perf should be in package linux-tools-common and each kernel versions has a 
dedicated linux-tool-common) package version.
$ dpkg -S $(which perf)
linux-tools-common: /usr/bin/perf
But on disk it's usually in /usr/bin.

Please can you check if it's in with:
$ dpkg -L linux-tools-common | grep perf$
/usr/bin/perf

In case it's not can you just take it temporarily from the last recent bionic 
package?
wget 
http://launchpadlibrarian.net/417515745/linux-tools-common_4.15.0-48.51_all.deb
dpkg-deb -x ./linux-tools-common_4.15.0-48.51_all.deb
I think that would be okay for this pre-test, since the perf tool wasn't 
touched, but just the kernel.

The verification during the SRU process later of course needs to be with
the proper package.

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

Title:
  perf top problem on z with Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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