[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-17 Thread Frank Heimes
On the kernel teams mailing list this was 'NACK'ed for focal, but only because 
it has already been applied from 5.4 stable.
I just double checked and the commit is in focal master (since 
Ubuntu-5.4-5.4.0-13.16 and there is currently 5.4.0.14.17 in focals release 
pocket).
Hence I change the focal entry to Fix Released and with that the project entry, 
too.

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

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-88.88

---
linux (4.15.0-88.88) bionic; urgency=medium

  * bionic/linux: 4.15.0-88.88 -proposed tracker (LP: #1862824)

  * Segmentation fault (kernel oops) with memory-hotplug in
ubuntu_kernel_selftests on Bionic kernel (LP: #1862312)
- Revert "mm/memory_hotplug: fix online/offline_pages called w.o.
  mem_hotplug_lock"
- mm/memory_hotplug: fix online/offline_pages called w.o. mem_hotplug_lock

linux (4.15.0-87.87) bionic; urgency=medium

  * bionic/linux: 4.15.0-87.87 -proposed tracker (LP: #1861165)

  * Bionic update: upstream stable patchset 2020-01-22 (LP: #1860602)
- scsi: lpfc: Fix discovery failures when target device connectivity bounces
- scsi: mpt3sas: Fix clear pending bit in ioctl status
- scsi: lpfc: Fix locking on mailbox command completion
- Input: atmel_mxt_ts - disable IRQ across suspend
- iommu/tegra-smmu: Fix page tables in > 4 GiB memory
- scsi: target: compare full CHAP_A Algorithm strings
- scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices
- scsi: csiostor: Don't enable IRQs too early
- powerpc/pseries: Mark accumulate_stolen_time() as notrace
- powerpc/pseries: Don't fail hash page table insert for bolted mapping
- powerpc/tools: Don't quote $objdump in scripts
- dma-debug: add a schedule point in debug_dma_dump_mappings()
- clocksource/drivers/asm9260: Add a check for of_clk_get
- powerpc/security/book3s64: Report L1TF status in sysfs
- powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning
- ext4: update direct I/O read lock pattern for IOCB_NOWAIT
- jbd2: Fix statistics for the number of logged blocks
- scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and 
WRITE(6)
- scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow
- f2fs: fix to update dir's i_pino during cross_rename
- clk: qcom: Allow constant ratio freq tables for rcg
- irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary
- irqchip: ingenic: Error out if IRQ domain creation failed
- fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned 
long
- scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences
- scsi: ufs: fix potential bug which ends in system hang
- powerpc/pseries/cmm: Implement release() function for sysfs device
- powerpc/security: Fix wrong message when RFI Flush is disable
- scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE
- clk: pxa: fix one of the pxa RTC clocks
- bcache: at least try to shrink 1 node in bch_mca_scan()
- HID: logitech-hidpp: Silence intermittent get_battery_capacity errors
- libnvdimm/btt: fix variable 'rc' set but not used
- HID: Improve Windows Precision Touchpad detection.
- scsi: pm80xx: Fix for SATA device discovery
- scsi: ufs: Fix error handing during hibern8 enter
- scsi: scsi_debug: num_tgts must be >= 0
- scsi: NCR5380: Add disconnect_mask module parameter
- scsi: iscsi: Don't send data to unbound connection
- scsi: target: iscsi: Wait for all commands to finish before freeing a
  session
- gpio: mpc8xxx: Don't overwrite default irq_set_type callback
- apparmor: fix unsigned len comparison with less than zero
- scripts/kallsyms: fix definitely-lost memory leak
- cdrom: respect device capabilities during opening action
- perf script: Fix brstackinsn for AUXTRACE
- perf regs: Make perf_reg_name() return "unknown" instead of NULL
- s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR
- libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h
- s390/cpum_sf: Check for SDBT and SDB consistency
- ocfs2: fix passing zero to 'PTR_ERR' warning
- kernel: sysctl: make drop_caches write-only
- userfaultfd: require CAP_SYS_PTRACE for UFFD_FEATURE_EVENT_FORK
- x86/mce: Fix possibly incorrect severity calculation on AMD
- net, sysctl: Fix compiler warning when only cBPF is present
- netfilter: nf_queue: enqueue skbs with NULL dst
- ALSA: hda - Downgrade error message for single-cmd fallback
- bonding: fix active-backup transition after link failure
- perf strbuf: Remove redundant va_end() in strbuf_addv()
- Make filldir[64]() verify the directory entry filename is valid
- filldir[64]: remove WARN_ON_ONCE() for bad directory entries
- netfilter: ebtables: compat: reject all padding in matches/watchers
- 6pack,mkiss: fix possible deadlock
- netfilter: bridge: make sure to pull arp header in br_nf_forward_arp()
- inetpeer: fix data-race in inet_putpeer / inet_putpeer
- net: add a READ_ONCE() in skb_peek_tail()
- net: icmp: fix data-race in cmp_global_allow()
- hrtimer: Annotate lockless access to timer->state
- spi: fsl: don't map irq during probe
- tty/serial: atmel: fix out of range clock divider handling
- pinctrl: baytrail: 

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.3.0-40.32

---
linux (5.3.0-40.32) eoan; urgency=medium

  * eoan/linux: 5.3.0-40.32 -proposed tracker (LP: #1861214)

  * No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after
modprobe sof (LP: #1860248)
- ASoC: SOF: Intel: fix HDA codec driver probe with multiple controllers

  * ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12)
(LP: #1852122)
- ocfs2: fix the crash due to call ocfs2_get_dlm_debug once less

  * QAT drivers for C3XXX and C62X not included as modules (LP: #1845959)
- [Config] CRYPTO_DEV_QAT_C3XXX=m, CRYPTO_DEV_QAT_C62X=m and
  CRYPTO_DEV_QAT_DH895xCC=m

  * Eoan update: upstream stable patchset 2020-01-24 (LP: #1860816)
- scsi: lpfc: Fix discovery failures when target device connectivity bounces
- scsi: mpt3sas: Fix clear pending bit in ioctl status
- scsi: lpfc: Fix locking on mailbox command completion
- Input: atmel_mxt_ts - disable IRQ across suspend
- f2fs: fix to update time in lazytime mode
- iommu: rockchip: Free domain on .domain_free
- iommu/tegra-smmu: Fix page tables in > 4 GiB memory
- dmaengine: xilinx_dma: Clear desc_pendingcount in xilinx_dma_reset
- scsi: target: compare full CHAP_A Algorithm strings
- scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices
- scsi: csiostor: Don't enable IRQs too early
- scsi: hisi_sas: Replace in_softirq() check in hisi_sas_task_exec()
- powerpc/pseries: Mark accumulate_stolen_time() as notrace
- powerpc/pseries: Don't fail hash page table insert for bolted mapping
- powerpc/tools: Don't quote $objdump in scripts
- dma-debug: add a schedule point in debug_dma_dump_mappings()
- leds: lm3692x: Handle failure to probe the regulator
- clocksource/drivers/asm9260: Add a check for of_clk_get
- clocksource/drivers/timer-of: Use unique device name instead of timer
- powerpc/security/book3s64: Report L1TF status in sysfs
- powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning
- ext4: update direct I/O read lock pattern for IOCB_NOWAIT
- ext4: iomap that extends beyond EOF should be marked dirty
- jbd2: Fix statistics for the number of logged blocks
- scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and 
WRITE(6)
- scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow
- f2fs: fix to update dir's i_pino during cross_rename
- clk: qcom: Allow constant ratio freq tables for rcg
- clk: clk-gpio: propagate rate change to parent
- irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary
- irqchip: ingenic: Error out if IRQ domain creation failed
- fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned 
long
- scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences
- PCI: rpaphp: Fix up pointer to first drc-info entry
- scsi: ufs: fix potential bug which ends in system hang
- powerpc/pseries/cmm: Implement release() function for sysfs device
- PCI: rpaphp: Don't rely on firmware feature to imply drc-info support
- PCI: rpaphp: Annotate and correctly byte swap DRC properties
- PCI: rpaphp: Correctly match ibm, my-drc-index to drc-name when using drc-
  info
- powerpc/security: Fix wrong message when RFI Flush is disable
- scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE
- clk: pxa: fix one of the pxa RTC clocks
- bcache: at least try to shrink 1 node in bch_mca_scan()
- HID: quirks: Add quirk for HP MSU1465 PIXART OEM mouse
- HID: logitech-hidpp: Silence intermittent get_battery_capacity errors
- ARM: 8937/1: spectre-v2: remove Brahma-B53 from hardening
- libnvdimm/btt: fix variable 'rc' set but not used
- HID: Improve Windows Precision Touchpad detection.
- HID: rmi: Check that the RMI_STARTED bit is set before unregistering the 
RMI
  transport device
- watchdog: Fix the race between the release of watchdog_core_data and cdev
- scsi: pm80xx: Fix for SATA device discovery
- scsi: ufs: Fix error handing during hibern8 enter
- scsi: scsi_debug: num_tgts must be >= 0
- scsi: NCR5380: Add disconnect_mask module parameter
- scsi: iscsi: Don't send data to unbound connection
- scsi: target: iscsi: Wait for all commands to finish before freeing a
  session
- gpio: mpc8xxx: Don't overwrite default irq_set_type callback
- apparmor: fix unsigned len comparison with less than zero
- scripts/kallsyms: fix definitely-lost memory leak
- powerpc: Don't add -mabi= flags when building with Clang
- cdrom: respect device capabilities during opening action
- perf script: Fix brstackinsn for AUXTRACE
- perf regs: Make perf_reg_name() return "unknown" instead of NULL
- s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR
- libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h
- 

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-07 Thread Frank Heimes
The commit "s390/qeth: fix false reporting of VNIC CHAR config failure"
is in focal master-next and tagged with:
Ubuntu-5.4-5.4.0-13.16
Ubuntu-5.4-5.4.0-14.17
We have currently the following kernels in focal:
 linux-generic | 5.4.0.12.15   | focal   | s390x
 linux-generic | 5.4.0.13.16   | focal-proposed  | s390x

Hence the above patch is not yet in 5.4.0.12.15 that's currently in the
release pocket, but already in proposed. Hence changing the focal status
here to Fix Committed.

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-04 Thread Frank Heimes
Adjusting tags according to previous comments.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-03 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-02-03 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-01-28 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1860523] Re: Fix misleading error message: Configuring the VNIC characteristics failed

2020-01-27 Thread Frank Heimes
Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2020-January/thread.html#107097
changing status to 'In Progress'

** Description changed:

+ SRU Justification:
+ --
+ 
+ [Impact]
+ 
+ * For devices that don't support the 'INVISIBLE' characteristic (ie.
+ OSA), the resulting IO failure raises the noisy error message
+ "Configuring the VNIC characteristics failed"
+ 
+ * The INVISIBLE characteristic unconditionally gets switched off, which
+ is reverted with this patch.
+ 
+ * For Internal Queued Direct communication (IQD) 'INVISIBLE' is off by
+ default.
+ 
+ * Hence the INVISIBLE characteristic case is unnecessary.
+ 
+ [Fix]
+ 
+ * 68c57bfd52836e31bff33e5e1fc64029749d2c35 68c57bf "s390/qeth: fix false
+ reporting of VNIC CHAR config failure"
+ 
+ * Upstream accepted with v5.5-rc5, but backport for 4.19-stable and
+ 5.4-stable here: https://git.kernel.org/pub/scm/linux/kernel/git/stable
+ /stable-queue.git
+ 
+ [Test Case]
+ 
+ * Configure an IBM z15 for LinuxONE III machine with at least one OSA
+ adapter.
+ 
+ * Check dmsg for message "Configuring the VNIC characteristics failed"
+ while setting an OSA device online.
+ 
+ [Regression Potential]
+ 
+ * The regression potential is low, since the patch is limited to a
+ single line
+ 
+ * again limited to the s390x architecture and once again limited to the
+ qeth network driver
+ 
+ * and on z15 hardware only.
+ 
+ [Other Info]
+ 
+ * This bug was identified at IBM while testing and is now rolled out to
+ several different kernels.
+ 
+ * Once the patch got applied to the Ubuntu kernel(s) and a verification
+ is required,
+ 
+ * this needs to be done by IBM, since Canonical doesn't have the needed
+ machine generation.
+ 
+ __
+ 
  The patch titled s390/qeth: fix false reporting of VNIC CHAR config failure
  has been added to the 4.19-stable tree which can be found at: 
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
  
  The filename of the patch is: s390-qeth-fix-false-reporting-of-vnic-
  char-config-failure.patch and it can be found in the queue-4.19
  subdirectory.
  
  Same for the the 5.4-stable tree which can be found at:
  http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-
  queue.git;a=summary
  
  The filename of the patch is: s390-qeth-fix-vnicc_is_in_use-if-rx_bcast-
  not-set.patch and it can be found in the queue-5.4 subdirectory.
  
  s390/qeth: fix false reporting of VNIC CHAR config failure
  commit 68c57bfd52836e31bff33e5e1fc64029749d2c35 upstream.
  
  Request: Please provide that fix also for Ubuntu 18.04 .
  
  Many thanks in advance

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

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

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

** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860523

Title:
  Fix misleading error message: Configuring the VNIC characteristics
  failed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs