[Kernel-packages] [Bug 1843790] Re: [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s, lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace generated and then failed to se

2019-09-25 Thread quanxian
5.3 mainline fixed. but no commit provided.

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

Title:
  [Thunderbolt][CML-U/S] After freeze sleep finished more than 30s,
  lspci trigger tbt in D0, "TX ring 0 is already enabled" Call Trace
  generated and then failed to send driver ready to ICM

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

Bug description:
  Description
  Platform: CML-U (CML-S no need TR AIC)

  TR AIC: rev41

  Linux kernel: 5.3.0-rc1

  No TBT device connected.

  Executed freeze sleep successfully, after freeze exit more than 30s,

  cat /sys/bus/thunderbolt/devices/domain0/boot_acl  and lspci to
  trigger TBT root port in D0.

  Then "TX ring 0 is already enabled" Call Trace generated, then failed
  to send driver ready to  ICM.

  Thunderbolt driver was down.
   

  [ 263.903342] LTP: starting TBT_XS_FUNC_RTD3_freeze_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_freeze)
  [ 264.010613] PM: suspend entry (s2idle)
  [ 286.868539] PM: suspend exit
  [ 313.202856] thunderbolt :03:00.0: stopping RX ring 0
  [ 313.204135] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [ 313.205565] thunderbolt :03:00.0: stopping TX ring 0
  [ 313.206842] thunderbolt :03:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [ 313.208018] thunderbolt :03:00.0: control channel stopped
  [ 321.432230] pcieport :02:01.0: pciehp: Slot(1): Link Up
  [ 321.433559] pcieport :02:04.0: pciehp: Slot(4-1): Link Up
  [ 322.550092] xhci_hcd :39:00.0: Refused to change power state, currently 
in D3
  [ 322.671084] thunderbolt :03:00.0: control channel starting...
  [ 322.672343] thunderbolt :03:00.0: starting TX ring 0
  [ 322.673601] thunderbolt :03:00.0: enabling interrupt at register 
0x38200 bit 0 (0x -> 0x)
  [ 322.674912] ---[ cut here ]---
  [ 322.676173] thunderbolt :03:00.0: interrupt for TX ring 0 is already 
enabled
  [ 322.706970] Call Trace:
  [ 322.708542] tb_ring_start+0x110/0x1a0 [thunderbolt]
  [ 322.710166] tb_ctl_start+0x36/0xc0 [thunderbolt]
  [ 322.711762] ? pci_restore_standard_config+0x50/0x50
  [ 322.71] ? pci_restore_standard_config+0x50/0x50
  [ 322.748162] thunderbolt :03:00.0: interrupt for RX ring 0 is already 
enabled
  [ 322.788047] ? pci_restore_standard_config+0x50/0x50
  [ 322.789901] ? pci_restore_standard_config+0x50/0x50
  [ 404.405929] thunderbolt :03:00.0: failed to send driver ready to ICM
  [ 405.596681] LTP: starting TBT_XS_FUNC_RTD3_S3_test (tbt_rtd3.sh -c 0 -s 
rtd3_host_s3)

  
  Target Release: 20.04
  Target Kernel: TBD

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

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


[Kernel-packages] [Bug 1845374] Re: Xenial update: 4.4.192 upstream stable release

2019-09-25 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Xenial update: 4.4.192 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  * net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ 
context
  * net: tc35815: Explicitly check NET_IP_ALIGN is not zero in tc35815_rx
  * Bluetooth: btqca: Add a short delay before downloading the NVM
  * ibmveth: Convert multicast list size for little-endian system
  * gpio: Fix build error of function redefinition
  * cxgb4: fix a memory leak bug
  * net: myri10ge: fix memory leaks
  * cx82310_eth: fix a memory leak bug
  * net: kalmia: fix memory leaks
  * wimax/i2400m: fix a memory leak bug
  * ravb: Fix use-after-free ravb_tstamp_skb
  * Tools: hv: kvp: eliminate 'may be used uninitialized' warning
  * IB/mlx4: Fix memory leaks
  * ceph: fix buffer free while holding i_ceph_lock in __ceph_setxattr()
  * KVM: arm/arm64: Only skip MMIO insn once
  * libceph: allow ceph_buffer_put() to receive a NULL ceph_buffer
  * spi: bcm2835aux: ensure interrupts are enabled for shared handler
  * spi: bcm2835aux: unifying code between polling and interrupt driven code
  * spi: bcm2835aux: remove dangerous uncontrolled read of fifo
  * spi: bcm2835aux: fix corruptions for longer spi transfers
  * Revert "x86/apic: Include the LDR when clearing out APIC registers"
  * net: fix skb use after free in netpoll
  * net: stmmac: dwmac-rk: Don't fail if phy regulator is absent
  * Linux 4.4.192

  
     4.4.192 upstream stable release
     from git://git.kernel.org/

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

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


[Kernel-packages] [Bug 1845036] Re: Xenial update: 4.4.191 upstream stable release

2019-09-25 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Xenial update: 4.4.191 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  * HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
  * MIPS: kernel: only use i8253 clocksource with periodic clockevent
  * netfilter: ebtables: fix a memory leak bug in compat
  * bonding: Force slave speed check after link state recovery for 802.3ad
  * can: dev: call netif_carrier_off() in register_candev()
  * st21nfca_connectivity_event_received: null check the allocation
  * st_nci_hci_connectivity_event_received: null check the allocation
  * ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
  * net: usb: qmi_wwan: Add the BroadMobi BM818 card
  * isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in 
start_isoc_chain()
  * isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the stack
  * perf bench numa: Fix cpu0 binding
  * can: sja1000: force the string buffer NULL-terminated
  * can: peak_usb: force the string buffer NULL-terminated
  * NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()
  * net: cxgb3_main: Fix a resource leak in a error path in 'init_one()'
  * net: hisilicon: make hip04_tx_reclaim non-reentrant
  * net: hisilicon: fix hip04-xmit never return TX_BUSY
  * net: hisilicon: Fix dma_map_single failed on arm64
  * libata: add SG safety checks in SFF pio transfers
  * selftests: kvm: Adding config fragments
  * HID: wacom: correct misreported EKR ring values
  * Revert "dm bufio: fix deadlock with loop device"
  * userfaultfd_release: always remove uffd flags and clear vm_userfaultfd_ctx
  * x86/retpoline: Don't clobber RFLAGS during CALL_NOSPEC on i386
  * x86/apic: Handle missing global clockevent gracefully
  * x86/boot: Save fields explicitly, zero out everything else
  * x86/boot: Fix boot regression caused by bootparam sanitizing
  * dm btree: fix order of block initialization in btree_split_beneath
  * dm space map metadata: fix missing store of apply_bops() return value
  * dm table: fix invalid memory accesses with too high sector number
  * cgroup: Disable IRQs while holding css_set_lock
  * net: arc_emac: fix koops caused by sk_buff free
  * siphash: implement HalfSipHash1-3 for hash tables
  * netfilter: ctnetlink: don't use conntrack/expect object addresses as id
  * netfilter: conntrack: Use consistent ct id hash calculation
  * Revert "perf test 6: Fix missing kvm module load for s390"
  * x86/pm: Introduce quirk framework to save/restore extra MSR registers 
around suspend/resume
  * x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
  * scsi: ufs: Fix NULL pointer dereference in ufshcd_config_vreg_hpm()
  * dmaengine: ste_dma40: fix unneeded variable warning
  * usb: gadget: composite: Clear "suspended" on reset/disconnect
  * usb: host: fotg2: restart hcd after port reset
  * tools: hv: fix KVP and VSS daemons exit code
  * watchdog: bcm2835_wdt: Fix module autoload
  * tcp: fix tcp_rtx_queue_tail in case of empty retransmit queue
  * ALSA: usb-audio: Fix a stack buffer overflow bug in check_input_term
  * ALSA: usb-audio: Fix an OOB bug in parse_audio_mixer_unit
  * tcp: make sure EPOLLOUT wont be missed
  * ALSA: seq: Fix potential concurrent access to the deleted pool
  * KVM: x86: Don't update RIP or do single-step on faulting emulation
  * x86/apic: Do not initialize LDR and DFR for bigsmp
  * x86/apic: Include the LDR when clearing out APIC registers
  * usb-storage: Add new JMS567 revision to unusual_devs
  * USB: cdc-wdm: fix race between write and disconnect due to flag abuse
  * usb: host: ohci: fix a race condition between shutdown and irq
  * USB: storage: ums-realtek: Update module parameter description for 
auto_delink_en
  * USB: storage: ums-realtek: Whitelist auto-delink support
  * ptrace,x86: Make user_64bit_mode() available to 32-bit builds
  * uprobes/x86: Fix detection of 32-bit user mode
  * mmc: sdhci-of-at91: add quirk for broken HS200
  * mmc: core: Fix init of SD cards reporting an invalid VDD range
  * stm class: Fix a double free of stm_source_device
  * VMCI: Release resource if the work is already queued
  * Revert "cfg80211: fix processing world regdomain when non modular"
  * mac80211: fix possible sta leak

[Kernel-packages] [Bug 1845395] Re: Xenial update: 4.4.193 upstream stable release

2019-09-25 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Xenial update: 4.4.193 upstream stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.193 upstream stable release
 from git://git.kernel.org/

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

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


[Kernel-packages] [Bug 1845038] Re: Xenial update: 4.4.190 upstream stable release

2019-09-25 Thread Khaled El Mously
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Xenial update: 4.4.190 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  * usb: iowarrior: fix deadlock on disconnect
  * sound: fix a memory leak bug
  * x86/mm: Check for pfn instead of page in vmalloc_sync_one()
  * x86/mm: Sync also unmappings in vmalloc_sync_all()
  * mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()
  * perf db-export: Fix thread__exec_comm()
  * usb: yurex: Fix use-after-free in yurex_delete
  * can: peak_usb: fix potential double kfree_skb()
  * netfilter: nfnetlink: avoid deadlock due to synchronous request_module
  * iscsi_ibft: make ISCSI_IBFT dependson ACPI instead of ISCSI_IBFT_FIND
  * mac80211: don't warn about CW params when not using them
  * hwmon: (nct6775) Fix register address and added missed tolerance for nct6106
  * cpufreq/pasemi: fix use-after-free in pas_cpufreq_cpu_init()
  * s390/qdio: add sanity checks to the fast-requeue path
  * ALSA: compress: Fix regression on compressed capture streams
  * ALSA: compress: Prevent bypasses of set_params
  * ALSA: compress: Be more restrictive about when a drain is allowed
  * perf probe: Avoid calling freeing routine multiple times for same pointer
  * ARM: davinci: fix sleep.S build error on ARMv4
  * scsi: megaraid_sas: fix panic on loading firmware crashdump
  * scsi: ibmvfc: fix WARN_ON during event pool release
  * tty/ldsem, locking/rwsem: Add missing ACQUIRE to read_failed sleep loop
  * perf/core: Fix creating kernel counters for PMUs that override event->cpu
  * can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices
  * can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices
  * hwmon: (nct7802) Fix wrong detection of in4 presence
  * ALSA: firewire: fix a memory leak bug
  * mac80211: don't WARN on short WMM parameters from AP
  * SMB3: Fix deadlock in validate negotiate hits reconnect
  * smb3: send CAP_DFS capability during session setup
  * mwifiex: fix 802.11n/WPA detection
  * scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
  * sh: kernel: hw_breakpoint: Fix missing break in switch statement
  * mm/memcontrol.c: fix use after free in mem_cgroup_iter()
  * ALSA: hda - Fix a memory leak bug
  * HID: holtek: test for sanity of intfdata
  * HID: hiddev: avoid opening a disconnected device
  * HID: hiddev: do cleanup in failure of opening a device
  * Input: kbtab - sanity check for endpoint type
  * Input: iforce - add sanity checks
  * net: usb: pegasus: fix improper read if get_registers() fail
  * xen/pciback: remove set but not used variable 'old_state'
  * irqchip/irq-imx-gpcv2: Forward irq type to parent
  * perf header: Fix divide by zero error if f_header.attr_size==0
  * perf header: Fix use of unitialized value warning
  * libata: zpodd: Fix small read overflow in zpodd_get_mech_type()
  * scsi: hpsa: correct scsi command status issue after reset
  * ata: libahci: do not complain in case of deferred probe
  * kbuild: modpost: handle KBUILD_EXTRA_SYMBOLS only for external modules
  * IB/core: Add mitigation for Spectre V1
  * ocfs2: remove set but not used variable 'last_hash'
  * asm-generic: fix -Wtype-limits compiler warnings
  * staging: comedi: dt3000: Fix signed integer overflow 'divider * base'
  * staging: comedi: dt3000: Fix rounding up of timer divisor
  * USB: core: Fix races in character device registration and deregistraion
  * usb: cdc-acm: make sure a refcount is taken early enough
  * USB: serial: option: add D-Link DWM-222 device ID
  * USB: serial: option: Add support for ZTE MF871A
  * USB: serial: option: add the BroadMobi BM818 card
  * USB: serial: option: Add Motorola modem UARTs
  * Backport minimal compiler_attributes.h to support GCC 9
  * include/linux/module.h: copy __init/__exit attrs to init/cleanup_module
  * arm64: compat: Allow single-byte watchpoints on all addresses
  * Input: psmouse - fix build error of multiple definition
  * asm-generic: default BUG_ON(x) to if(x)BUG()
  * scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
  * RDMA: Directly cast the sockaddr union to sockaddr
  * IB/mlx5: Make coding style more consistent
  * x86/vdso: Remove direct HPET access through the vDSO
  * iommu/amd: Move iommu_init_pci() to .init section
  * 

[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )

2019-09-25 Thread Refrain
https://bugs.launchpad.net/psensor/+bug/1842525

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress
Status in libatasmart source package in Trusty:
  Confirmed
Status in libatasmart source package in Xenial:
  Confirmed
Status in libatasmart source package in Yakkety:
  Confirmed

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

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

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


[Kernel-packages] [Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)

2019-09-25 Thread Khaled El Mously
** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  /proc/self/maps paths missing on live session (was vlc won't start;
  eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate
  dailies)

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

Bug description:
  SRU Justification

  Impact: A patch to enable mounting overlayfs over shiftfs introduced a
  regression in /proc/pid/maps when a proc mount over an overlayfs mount
  is accessed from within a chroot. All paths within the file are /
  instead of paths to the files backing memory-mapped regions. This is
  causing issues in several different configurations.

  Fix: Revert the offending patch.

  Test Case: A simple reproducer can be found attached in lp1842382.sh.

  Regression Potential: This reverts to the previous behavior. Mounting
  overlayfs over shiftfs will not work until a fixed patch is applied.

  ---

  Using Lubuntu 19.10 daily 'live' :   (later confirmed with 
Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present)
  From menu option, from pcmanfm-qt (trying to open an appropriate file), or 
from terminal I've been unable to start vlc.

  lubuntu@lubuntu:~$ vlc
  VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
  lubuntu@lubuntu:~$

  No crash reports are visible (/var/crash/ is empty) and I see no
  reason, but I cannot get vlc to play files, or open.  I'll continue to
  explore as I'm able.

  QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: vlc 3.0.8-2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.415
  CurrentDesktop: LXQt
  Date: Tue Sep  3 06:03:17 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902)
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1844558] Re: Bionic update: upstream stable patchset 2019-09-18

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

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

Title:
  Bionic update: upstream stable patchset 2019-09-18

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-09-18

  Ported from the following upstream stable releases:
  v4.14.144, v4.19.73

     from git://git.kernel.org/

  ALSA: hda - Fix potential endless loop at applying quirks
  ALSA: hda/realtek - Fix overridden device-specific initialization
  ALSA: hda/realtek - Fix the problem of two front mics on a ThinkCentre
  sched/fair: Don't assign runtime for throttled cfs_rq
  drm/vmwgfx: Fix double free in vmw_recv_msg()
  xfrm: clean up xfrm protocol checks
  PCI: designware-ep: Fix find_first_zero_bit() usage
  PCI: dra7xx: Fix legacy INTD IRQ handling
  vhost/test: fix build for vhost test
  batman-adv: fix uninit-value in batadv_netlink_get_ifindex()
  batman-adv: Only read OGM tvlv_len after buffer len check
  hv_sock: Fix hang when a connection is closed
  powerpc/64: mark start_here_multiplatform as __ref
  arm64: dts: rockchip: enable usb-host regulators at boot on rk3328-rock64
  scripts/decode_stacktrace: match basepath using shell prefix operator, not 
regex
  clk: s2mps11: Add used attribute to s2mps11_dt_match
  kernel/module: Fix mem leak in module_add_modinfo_attrs
  ALSA: hda/realtek - Enable internal speaker & headset mic of ASUS UX431FL
  {nl,mac}80211: fix interface combinations on crypto controlled devices
  x86/ftrace: Fix warning and considate ftrace_jmp_replace() and 
ftrace_call_replace()
  media: stm32-dcmi: fix irq = 0 case
  modules: always page-align module section allocations
  scsi: qla2xxx: Move log messages before issuing command to firmware
  keys: Fix the use of the C++ keyword "private" in uapi/linux/keyctl.h
  Drivers: hv: kvp: Fix two "this statement may fall through" warnings
  remoteproc: qcom: q6v5-mss: add SCM probe dependency
  KVM: x86: hyperv: enforce vp_index < KVM_MAX_VCPUS
  KVM: x86: hyperv: consistently use 'hv_vcpu' for 'struct kvm_vcpu_hv' 
variables
  drm/i915: Fix intel_dp_mst_best_encoder()
  drm/i915: Rename PLANE_CTL_DECOMPRESSION_ENABLE
  drm/i915/gen9+: Fix initial readout for Y tiled framebuffers
  drm/atomic_helper: Disallow new modesets on unregistered connectors
  Drivers: hv: kvp: Fix the indentation of some "break" statements
  Drivers: hv: kvp: Fix the recent regression caused by incorrect clean-up
  drm/amd/dm: Understand why attaching path/tile properties are needed
  ARM: davinci: da8xx: define gpio interrupts as separate resources
  ARM: davinci: dm365: define gpio interrupts as separate resources
  ARM: davinci: dm646x: define gpio interrupts as separate resources
  ARM: davinci: dm355: define gpio interrupts as separate resources
  ARM: davinci: dm644x: define gpio interrupts as separate resources
  media: vim2m: use workqueue
  media: vim2m: use cancel_delayed_work_sync instead of flush_schedule_work
  drm/i915: Restore sane defaults for KMS on GEM error load
  KVM: PPC: Book3S HV: Fix race between kvm_unmap_hva_range and MMU mode switch
  Btrfs: clean up scrub is_dev_replace parameter
  Btrfs: fix deadlock with memory reclaim during scrub
  btrfs: Remove extent_io_ops::fill_delalloc
  btrfs: Fix error handling in btrfs_cleanup_ordered_extents
  scsi: megaraid_sas: Fix combined reply queue mode detection
  scsi: megaraid_sas: Add check for reset adapter bit
  media: vim2m: only cancel work if it is for right context
  ARC: show_regs: lockdep: re-enable preemption
  ARC: mm: do_page_fault fixes #1: relinquish mmap_sem if signal arrives while 
handle_mm_fault
  IB/uverbs: Fix OOPs upon device disassociation
  drm/vblank: Allow dynamic per-crtc max_vblank_count
  drm/i915/ilk: Fix warning when reading emon_status with no output
  mfd: Kconfig: Fix I2C_DESIGNWARE_PLATFORM dependencies
  tpm: Fix some name collisions with drivers/char/tpm.h
  bcache: replace hard coded number with BUCKET_GC_GEN_MAX
  bcache: treat stale && dirty keys as bad keys
  KVM: VMX: Compare only a single byte for VMCS' "launched" in vCPU-run
  iio: adc: exynos-adc: Add S5PV210 variant
  iio: adc: exynos-adc: Use proper number of channels for Exynos4x12
  drm/nouveau: Don't WARN_ON VCPI allocation failures
  

[Kernel-packages] [Bug 1843338] Re: Bionic update: upstream stable patchset 2019-09-09

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

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

Title:
  Bionic update: upstream stable patchset 2019-09-09

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-09-09

  Ported from the following upstream stable releases: 
  v4.14.142, v4.19.70, 
 v4.19.71 

     from git://git.kernel.org/

  dmaengine: ste_dma40: fix unneeded variable warning
  auxdisplay: panel: need to delete scan_timer when misc_register fails in 
panel_attach
  iommu/dma: Handle SG length overflow better
  usb: gadget: composite: Clear "suspended" on reset/disconnect
  usb: gadget: mass_storage: Fix races between fsg_disable and fsg_set_alt
  xen/blkback: fix memory leaks
  i2c: rcar: avoid race when unregistering slave client
  i2c: emev2: avoid race when unregistering slave client
  drm/ast: Fixed reboot test may cause system hanged
  usb: host: fotg2: restart hcd after port reset
  tools: hv: fix KVP and VSS daemons exit code
  watchdog: bcm2835_wdt: Fix module autoload
  drm/bridge: tfp410: fix memleak in get_modes()
  scsi: ufs: Fix RX_TERMINATION_FORCE_ENABLE define value
  drm/tilcdc: Register cpufreq notifier after we have initialized crtc
  ALSA: usb-audio: Fix a stack buffer overflow bug in check_input_term
  ALSA: usb-audio: Fix an OOB bug in parse_audio_mixer_unit
  net/smc: make sure EPOLLOUT is raised
  tcp: make sure EPOLLOUT wont be missed
  mm/zsmalloc.c: fix build when CONFIG_COMPACTION=n
  ALSA: line6: Fix memory leak at line6_init_pcm() error path
  ALSA: seq: Fix potential concurrent access to the deleted pool
  kvm: x86: skip populating logical dest map if apic is not sw enabled
  KVM: x86: Don't update RIP or do single-step on faulting emulation
  x86/apic: Do not initialize LDR and DFR for bigsmp
  x86/apic: Include the LDR when clearing out APIC registers
  ftrace: Fix NULL pointer dereference in t_probe_next()
  ftrace: Check for successful allocation of hash
  ftrace: Check for empty hash and comment the race with registering probes
  usb-storage: Add new JMS567 revision to unusual_devs
  USB: cdc-wdm: fix race between write and disconnect due to flag abuse
  usb: chipidea: udc: don't do hardware access if gadget has stopped
  usb: host: ohci: fix a race condition between shutdown and irq
  usb: host: xhci: rcar: Fix typo in compatible string matching
  USB: storage: ums-realtek: Update module parameter description for 
auto_delink_en
  USB: storage: ums-realtek: Whitelist auto-delink support
  uprobes/x86: Fix detection of 32-bit user mode
  mmc: sdhci-of-at91: add quirk for broken HS200
  mmc: core: Fix init of SD cards reporting an invalid VDD range
  stm class: Fix a double free of stm_source_device
  intel_th: pci: Add support for another Lewisburg PCH
  intel_th: pci: Add Tiger Lake support
  drm/i915: Don't deballoon unused ggtt drm_mm_node in linux guest
  VMCI: Release resource if the work is already queued
  crypto: ccp - Ignore unconfigured CCP device on suspend/resume
  Revert "cfg80211: fix processing world regdomain when non modular"
  mac80211: fix possible sta leak
  KVM: PPC: Book3S: Fix incorrect guest-to-user-translation error handling
  KVM: arm/arm64: vgic: Fix potential deadlock when ap_list is long
  KVM: arm/arm64: vgic-v2: Handle SGI bits in GICD_I{S,C}PENDR0 as WI
  NFS: Clean up list moves of struct nfs_page
  NFSv4/pnfs: Fix a page lock leak in nfs_pageio_resend()
  NFS: Pass error information to the pgio error cleanup routine
  NFS: Ensure O_DIRECT reports an error if the bytes read/written is 0
  i2c: piix4: Fix port selection for AMD Family 16h Model 30h
  x86/ptrace: fix up botched merge of spectrev1 fix
  Revert "ASoC: Fail card instantiation if DAI format setup fails"
  nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns
  afs: Fix the CB.ProbeUuid service handler to reply correctly
  dmaengine: stm32-mdma: Fix a possible null-pointer dereference in 
stm32_mdma_irq_handler()
  omap-dma/omap_vout_vrfb: fix off-by-one fi value
  arm64: cpufeature: Don't treat granule sizes as strict
  tools: hv: fixed Python pep8/flake8 warnings for lsvmbus
  ipv4/icmp: fix rt dst dev null pointer dereference
  ALSA: hda - Fixes inverted 

[Kernel-packages] [Bug 1843463] Re: Bionic update: upstream stable patchset 2019-09-10

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

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

Title:
  Bionic update: upstream stable patchset 2019-09-10

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-09-10

    Ported from the following upstream stable releases:
     v4.14.143, v4.19.72

     from git://git.kernel.org/

  net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ 
context
  hv_netvsc: Fix a warning of suspicious RCU usage
  net: tc35815: Explicitly check NET_IP_ALIGN is not zero in tc35815_rx
  Bluetooth: btqca: Add a short delay before downloading the NVM
  ibmveth: Convert multicast list size for little-endian system
  gpio: Fix build error of function redefinition
  drm/mediatek: use correct device to import PRIME buffers
  drm/mediatek: set DMA max segment size
  cxgb4: fix a memory leak bug
  liquidio: add cleanup in octeon_setup_iq()
  net: myri10ge: fix memory leaks
  lan78xx: Fix memory leaks
  vfs: fix page locking deadlocks when deduping files
  cx82310_eth: fix a memory leak bug
  net: kalmia: fix memory leaks
  wimax/i2400m: fix a memory leak bug
  ravb: Fix use-after-free ravb_tstamp_skb
  kprobes: Fix potential deadlock in kprobe_optimizer()
  HID: cp2112: prevent sleeping function called from invalid context
  Input: hyperv-keyboard: Use in-place iterator API in the channel callback
  Tools: hv: kvp: eliminate 'may be used uninitialized' warning
  IB/mlx4: Fix memory leaks
  ceph: fix buffer free while holding i_ceph_lock in __ceph_setxattr()
  ceph: fix buffer free while holding i_ceph_lock in __ceph_build_xattrs_blob()
  ceph: fix buffer free while holding i_ceph_lock in fill_inode()
  KVM: arm/arm64: Only skip MMIO insn once
  libceph: allow ceph_buffer_put() to receive a NULL ceph_buffer
  spi: bcm2835aux: unifying code between polling and interrupt driven code
  spi: bcm2835aux: remove dangerous uncontrolled read of fifo
  spi: bcm2835aux: fix corruptions for longer spi transfers
  net: fix skb use after free in netpoll
  net_sched: fix a NULL pointer deref in ipt action
  net: stmmac: dwmac-rk: Don't fail if phy regulator is absent
  tcp: inherit timestamp on mtu probe
  tcp: remove empty skb from write queue in error cases
  net: sched: act_sample: fix psample group handling on overwrite
  mld: fix memory leak in mld_del_delrec()
  x86/boot: Preserve boot_params.secure_boot from sanitizing
  tools: bpftool: fix error message (prog -> object)
  scsi: qla2xxx: Fix gnl.l memory leak on adapter init failure
  afs: Fix leak in afs_lookup_cell_rcu()
  UBUNTU: upstream stable to v4.14.143, v4.19.72

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

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


[Kernel-packages] [Bug 1845266] Re: Bionic update: upstream stable patchset 2019-09-24

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

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

Title:
  Bionic update: upstream stable patchset 2019-09-24

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-09-24

  Ported from the following upstream stable releases:
  v4.14.145, v4.19.74
  v4.14.146, v4.19.75

     from git://git.kernel.org/

  bridge/mdb: remove wrong use of NLM_F_MULTI
  cdc_ether: fix rndis support for Mediatek based smartphones
  ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()'
  isdn/capi: check message length in capi_write()
  net: Fix null de-reference of device refcount
  net: gso: Fix skb_segment splat when splitting gso_size mangled skb having 
linear-headed frag_list
  net: phylink: Fix flow control resolution
  sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero
  sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()'
  sctp: use transport pf_retrans in sctp_do_8_2_transport_strike
  tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR
  tipc: add NULL pointer check before calling kfree_rcu
  tun: fix use-after-free when register netdev failed
  btrfs: compression: add helper for type to string conversion
  btrfs: correctly validate compression type
  Revert "MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur"
  gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist
  gpio: fix line flag validation in linehandle_create
  gpio: fix line flag validation in lineevent_create
  Btrfs: fix assertion failure during fsync and use of stale transaction
  genirq: Prevent NULL pointer dereference in resend_irqs()
  KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl
  KVM: x86: work around leak of uninitialized stack contents
  KVM: nVMX: handle page fault in vmread
  MIPS: VDSO: Prevent use of smp_processor_id()
  MIPS: VDSO: Use same -m%-float cflag as the kernel proper
  powerpc: Add barrier_nospec to raw_copy_in_user()
  drm/meson: Add support for XBGR & ABGR formats
  clk: rockchip: Don't yell about bad mmc phases when getting
  mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue
  PCI: Always allow probing with driver_override
  ubifs: Correctly use tnc_next() in search_dh_cookie()
  driver core: Fix use-after-free and double free on glue directory
  crypto: talitos - check AES key size
  crypto: talitos - fix CTR alg blocksize
  crypto: talitos - check data blocksize in ablkcipher.
  crypto: talitos - fix ECB algs ivsize
  crypto: talitos - Do not modify req->cryptlen on decryption.
  crypto: talitos - HMAC SNOOP NO AFEU mode requires SW icv checking.
  firmware: ti_sci: Always request response from firmware
  drm/mediatek: mtk_drm_drv.c: Add of_node_put() before goto
  Revert "Bluetooth: btusb: driver to enable the usb-wakeup feature"
  platform/x86: pmc_atom: Add CB4063 Beckhoff Automation board to 
critclk_systems DMI table
  nvmem: Use the same permissions for eeprom as for nvmem
  x86/build: Add -Wnoaddress-of-packed-member to REALMODE_CFLAGS, to silence 
GCC9 build warning
  ixgbe: Prevent u8 wrapping of ITR value to something less than 10us
  x86/purgatory: Change compiler flags from -mcmodel=kernel to -mcmodel=large 
to fix kexec relocation errors
  modules: fix BUG when load module with rodata=n
  modules: fix compile error if don't have strict module rwx
  UBUNTU: upstream stable to v4.14.145, v4.19.74
  HID: wacom: generic: read HID_DG_CONTACTMAX from any feature report
  Input: elan_i2c - remove Lenovo Legion Y7000 PnpID
  powerpc/mm/radix: Use the right page size for vmemmap mapping
  USB: usbcore: Fix slab-out-of-bounds bug during device reset
  phy: renesas: rcar-gen3-usb2: Disable clearing VBUS in over-current
  media: tm6000: double free if usb disconnect while streaming
  xen-netfront: do not assume sk_buff_head list is empty in error handling
  net_sched: let qdisc_put() accept NULL pointer
  KVM: coalesced_mmio: add bounds checking
  firmware: google: check if size is valid when decoding VPD data
  serial: sprd: correct the wrong sequence of arguments
  tty/serial: atmel: reschedule TX after RX was started
  mwifiex: Fix three heap overflow at parsing element in 

[Kernel-packages] [Bug 1834681] Re: Enable napi_tx for GCP/GKE kernels

2019-09-25 Thread Khaled El Mously
** Changed in: linux-gcp (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  Enable napi_tx for GCP/GKE kernels

Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gke-4.15 package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Committed
Status in linux-gke-4.15 source package in Xenial:
  Invalid
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-gcp source package in Bionic:
  Invalid
Status in linux-gke-4.15 source package in Bionic:
  Fix Committed
Status in linux-gke-5.0 source package in Bionic:
  In Progress
Status in linux-gcp source package in Disco:
  Fix Committed
Status in linux-gke-4.15 source package in Disco:
  Invalid
Status in linux-gke-5.0 source package in Disco:
  Invalid

Bug description:
  Background: Napi_tx is a Linux kernel feature that makes the virtio
  driver call the skb destructor after the packets are actually “out”
  (i.e., at TX completion interrupt), as opposed to immediately after
  the packets are enqueued. This provides socket backpressure and is
  critical for features such as TSQ. Enabling napi_tx in Cloud guests is
  an indispensable link in the chain of end-to-end backpressure from
  USPS all the way up to the guest applications. It would help reduce
  bufferbloat, packet drops and/or avoid HoL blocking when the traffic
  from the VMs are rate limited (due to congestion/BwE/etc).

  The GCP networking engineering teams have asked us to include and
  enable napi_tx on the major guest OS's on the platform. They have 6
  months of performance and regression testing and are comfortable
  moving forward with this broadly.

  The main request is to change this module parameter: 
  +++ b/drivers/net/virtio_net.c 
  @@ -26,7 +26,7 @@ 
  static int napi_weight = NAPI_POLL_WEIGHT; 
  module_param(napi_weight, int, 0444); 

  -static bool csum = true, gso = true, napi_tx; 
  +static bool csum = true, gso = true, napi_tx = true; 

  That is either the above kernel change or a configuration change at
  module load. Note that that also gives us a simple resolution in the
  unlikely case that this causes a regression on some workloads.

  Besides the main switch, kernels need these other prerequisite
  patches:

  The main feature, in 4.12-rc1:

  1d11e732e7d50 virtio-net: use netif_tx_napi_add for tx napi 
  78a57b482aa53 virtio-net: on tx, only call napi_disable if tx napi is on 
  bdb12e0d2ffc8 virtio-net: keep tx interrupts disabled unless kick 
  7b0411ef4aa69 virtio-net: clean tx descriptors from rx napi 
  ea7735d97ba90 virtio-net: move free_old_xmit_skbs 
  b92f1e6751a6a virtio-net: transmit napi 
  e4e8452a4ab30 virtio-net: napi helper functions 

  Virtio-net queue affinity, in 4.19-rc1:

  2ca653d607ce5 virtio_net: Stripe queue affinities across cores. 
  19e226e8cc5da virtio: Make vp_set_vq_affinity() take a mask. 
  9af18e56d43ca cpumask: make cpumask_next_wrap available without smp 

  A nice to have is ethtool support to test whether the feature is
  enabled, in 5.1-rc1:

  133bbb18ab1a2 virtio-net: per-queue RPS config

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

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


[Kernel-packages] [Bug 1842502] Re: TC filters are broken on Mellanox after upstream stable updates

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

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

Title:
  TC filters are broken on Mellanox after upstream stable updates

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

Bug description:
  [Impact]

  Mellanox TC filters don't work for some key rules after the Bionic
  4.15 stable patchset 2019-07-12 update (LP: #1836426). The offending
  commit is ("net/mlx5e: Set vlan masks for all offloaded TC rules").

  This causes fatal network connectivity issues for projects that use
  the Mellanox ConnectX 5 NIC.

  
  [Test Case]

  TBD.

  
  [Fix]

  Backport the following upstream commit (which fixes the offending commit) and 
its prerequisites:
  d3a80bb5a3ea ("net/mlx5e: Don't match on vlan non-existence if ethertype is 
wildcarded")

  
  [Regression Potential]

  Low. Changes are isolated and limited to the mlx5_core driver and all
  commits are in upstream stable v4.19.y.

  
  [Original description]

  The following upstream fix was missing from the latest upstream stable
  update (LP: # and LP1839376: #1839213):

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

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

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


[Kernel-packages] [Bug 1836440] Re: RTL8723BS wifi not working

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

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

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

Title:
  RTL8723BS wifi not working

Status in linux package in Ubuntu:
  Expired
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  I have a Chuwi Hi10 Air laptop which has rtl8723bs wifi chip. Wifi
  works in Ubuntu 18.04 LTS, it works in Fedora 30 as well. But not in
  Ubuntu 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-firmware 1.178.2
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Sat Jul 13 14:50:45 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-07-12 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1845411] ProcCpuinfoMinimal.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291355/+files/ProcCpuinfoMinimal.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: 

[Kernel-packages] [Bug 1845411] WifiSyslog.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291362/+files/WifiSyslog.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer 

[Kernel-packages] [Bug 1845411] RfKill.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1845411/+attachment/5291360/+files/RfKill.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. 

[Kernel-packages] [Bug 1845411] ProcInterrupts.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291357/+files/ProcInterrupts.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK 

[Kernel-packages] [Bug 1845411] ProcEnviron.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291356/+files/ProcEnviron.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer 

[Kernel-packages] [Bug 1845411] ProcModules.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291358/+files/ProcModules.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer 

[Kernel-packages] [Bug 1845411] PulseList.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291359/+files/PulseList.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer 

[Kernel-packages] [Bug 1845411] UdevDb.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1845411/+attachment/5291361/+files/UdevDb.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. 

[Kernel-packages] [Bug 1845411] CurrentDmesg.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291350/+files/CurrentDmesg.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK 

[Kernel-packages] [Bug 1845411] CRDA.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1845411/+attachment/5291349/+files/CRDA.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise 

[Kernel-packages] [Bug 1845411] Lsusb.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1845411/+attachment/5291353/+files/Lsusb.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise 

[Kernel-packages] [Bug 1845411] IwConfig.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291351/+files/IwConfig.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. 

[Kernel-packages] [Bug 1845411] ProcCpuinfo.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1845411/+attachment/5291354/+files/ProcCpuinfo.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer 

[Kernel-packages] [Bug 1845411] Lspci.txt

2019-09-25 Thread Michael
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1845411/+attachment/5291352/+files/Lspci.txt

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise 

[Kernel-packages] [Bug 1845411] Re: Alt-Tab runs by itself. Active screen changes for no reason

2019-09-25 Thread Michael
apport information

** Tags added: apport-collected sylvia

** Description changed:

  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.
  
   ubuntu-bug linux
  
  *** Collecting problem information
  
  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..
  
  *** Problem in linux-image-4.15.0-64-generic
  
  The problem cannot be reported:
  
  This is not an official Linux package. Please remove any third party
  package and try again.
  
  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
  
  Output of sudo lspci -vnvn > lspci-vnvn.log =
  
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore
  
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915
  
  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
  
  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
  
  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
  
  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP CSME HECI [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- 

[Kernel-packages] [Bug 1845411] Re: Alt-Tab runs by itself. Active screen changes for no reason

2019-09-25 Thread Michael
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP CSME HECI [1043:1480]
Control: I/O- Mem+ 

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

2019-09-25 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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


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

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

apport-collect 1845411

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

Title:
  Alt-Tab runs by itself. Active screen changes for no reason

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am running Linux Mint 18.3 and Kernel 4.15.0-64.
  I only installed a couple of days ago.
  When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

   ubuntu-bug linux

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Problem in linux-image-4.15.0-64-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  Output of cat /proc/version_signature > version.log =
  Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

  Output of sudo lspci -vnvn > lspci-vnvn.log =

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise 
Point-LP Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise 

[Kernel-packages] [Bug 1845411] [NEW] Alt-Tab runs by itself. Active screen changes for no reason

2019-09-25 Thread Michael
Public bug reported:

I am running Linux Mint 18.3 and Kernel 4.15.0-64.
I only installed a couple of days ago.
When I have multiple screens open, Alt-Tab type behavior causes the active 
window to jump to another.

 ubuntu-bug linux

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..

*** Problem in linux-image-4.15.0-64-generic

The problem cannot be reported:

This is not an official Linux package. Please remove any third party
package and try again.

Output of cat /proc/version_signature > version.log =
Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18

Output of sudo lspci -vnvn > lspci-vnvn.log =

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1480]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee08004  Data: 4022
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] #1b
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] #13
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:13.0 Non-VGA unclassified device []: Intel Corporation Sunrise Point-LP 
Integrated Sensor Hub [8086:9d35] (rev 21)
Subsystem: Intel Corporation Sunrise Point-LP Integrated Sensor Hub 
[8086:9d35]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Serial IO I2C 
Controller [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP CSME HECI [1043:1480]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, 

[Kernel-packages] [Bug 1845405] [NEW] Xenial update: 4.4.194 upstream stable release

2019-09-25 Thread Connor Kuehl
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:

   4.4.194 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

Title:
  Xenial update: 4.4.194 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.194 upstream stable release
 from git://git.kernel.org/

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

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


[Kernel-packages] [Bug 1842037] Re: Oops when Kerberos credentials are invalid

2019-09-25 Thread Matthew Ruffell
Hi Frank,

Just checking in to see how the test kernel is going. Does it fix your
problem of the kernel crashing when users have invalid kerberos
credentials?

Did you try it on the original server which crashes frequently? Has it
made things more stable?

Did you have an opportunity to try the reproducer I linked you in my
previous message?

Let me know how things are going, when you have had a chance to test the
kernel.

Thanks,
Matthew

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

Title:
  Oops when Kerberos credentials are invalid

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  In Progress

Bug description:
  There's a bug in Linux Kernel 5.0 which is triggered by invalid
  credentials when the NFS clients is trying to aquire them via GSSD.
  This affects NFS-Shares that are protected by krb5* security. They
  become unusable until the system is re-booted. The problem is quite
  severe on terminal servers with multiple users - some of them not
  caring about refreshing their kerberos tickets.

  A fix is available here:

  


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

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


[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage

2019-09-25 Thread constantoverride
the initial patch I've attached/tried (in #89) was crap, but now I'm
successfully using this one le9h.patch (attached)

also here:
https://gist.github.com/howaboutsynergy/04fd9be927835b055ac15b8b64658e85

there are similar patches from years ago made by some devs, if you
follow those urls (mentioned in patch) you can see them

Either way, this will prevent Active(file) to get lower than the set
value, more or less. As a workaround is good enough for me. (far better
than my initial attempt)

** Patch added: "keep Active(file) above certain threshold to avoid constant 
disk reading when memory pressure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+attachment/5291340/+files/le9h.patch

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

Title:
  When DMA is disabled system freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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


[Kernel-packages] [Bug 1845371] Re: eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 20:41 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 20:41 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

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


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

2019-09-25 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1845128
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Tuesday, 24. September 2019 12:17 UTC
+ phase: Signoff
+ phase-changed: Wednesday, 25. September 2019 22:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1844346
  trackers:
bionic/linux-gcp-edge: bug 1844345
bionic/linux-gcp/gcp-kernel: bug 1845126
  variant: debs

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  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: 1845128
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Signoff
  phase-changed: Wednesday, 25. September 2019 22:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1844346
  trackers:
bionic/linux-gcp-edge: bug 1844345
bionic/linux-gcp/gcp-kernel: bug 1845126
  variant: debs

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

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


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

2019-09-25 Thread Adam Conrad
Hello Mauricio, or anyone else affected,

Accepted debian-installer into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu543.11 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: debian-installer (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

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

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in debian-installer source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in debian-installer source package in Disco:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in debian-installer source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

     No regressions observed between the original and test kernels.

  [Regression Potential]

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

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

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

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

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

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

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


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

2019-09-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/debian-installer/bionic-proposed

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

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

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in debian-installer source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in debian-installer source package in Disco:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in debian-installer source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

     No regressions observed between the original and test kernels.

  [Regression Potential]

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

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

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

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

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

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

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


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

2019-09-25 Thread Eric Desrochers
Sponsored in Bionic.

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

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

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in debian-installer source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in debian-installer source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in debian-installer source package in Disco:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in debian-installer source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

     No regressions observed between the original and test kernels.

  [Regression Potential]

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1845395] [NEW] Xenial update: 4.4.193 upstream stable release

2019-09-25 Thread Connor Kuehl
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:

   4.4.193 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

Title:
  Xenial update: 4.4.193 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.193 upstream stable release
 from git://git.kernel.org/

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

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


[Kernel-packages] [Bug 1845395] Re: Xenial update: 4.4.193 upstream stable release

2019-09-25 Thread Connor Kuehl
Already applied:

* vhost: make sure log_num < in_num

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

Title:
  Xenial update: 4.4.193 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.193 upstream stable release
 from git://git.kernel.org/

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

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


[Kernel-packages] [Bug 1844140] Re: eoan/linux-gcp: 5.3.0-1002.2 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1845105
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 16:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1845105
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 16:31 UTC
  reason:
promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

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


[Kernel-packages] [Bug 1845374] Re: Xenial update: 4.4.192 upstream stable release

2019-09-25 Thread Connor Kuehl
** 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:
+ * net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ 
context
+ * net: tc35815: Explicitly check NET_IP_ALIGN is not zero in tc35815_rx
+ * Bluetooth: btqca: Add a short delay before downloading the NVM
+ * ibmveth: Convert multicast list size for little-endian system
+ * gpio: Fix build error of function redefinition
+ * cxgb4: fix a memory leak bug
+ * net: myri10ge: fix memory leaks
+ * cx82310_eth: fix a memory leak bug
+ * net: kalmia: fix memory leaks
+ * wimax/i2400m: fix a memory leak bug
+ * ravb: Fix use-after-free ravb_tstamp_skb
+ * Tools: hv: kvp: eliminate 'may be used uninitialized' warning
+ * IB/mlx4: Fix memory leaks
+ * ceph: fix buffer free while holding i_ceph_lock in __ceph_setxattr()
+ * KVM: arm/arm64: Only skip MMIO insn once
+ * libceph: allow ceph_buffer_put() to receive a NULL ceph_buffer
+ * spi: bcm2835aux: ensure interrupts are enabled for shared handler
+ * spi: bcm2835aux: unifying code between polling and interrupt driven code
+ * spi: bcm2835aux: remove dangerous uncontrolled read of fifo
+ * spi: bcm2835aux: fix corruptions for longer spi transfers
+ * Revert "x86/apic: Include the LDR when clearing out APIC registers"
+ * net: fix skb use after free in netpoll
+ * net: stmmac: dwmac-rk: Don't fail if phy regulator is absent
+ * Linux 4.4.192
  
-4.4.192 upstream stable release
-from git://git.kernel.org/
+ 
+    4.4.192 upstream stable release
+    from git://git.kernel.org/

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

Title:
  Xenial update: 4.4.192 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  * net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ 
context
  * net: tc35815: Explicitly check NET_IP_ALIGN is not zero in tc35815_rx
  * Bluetooth: btqca: Add a short delay before downloading the NVM
  * ibmveth: Convert multicast list size for little-endian system
  * gpio: Fix build error of function redefinition
  * cxgb4: fix a memory leak bug
  * net: myri10ge: fix memory leaks
  * cx82310_eth: fix a memory leak bug
  * net: kalmia: fix memory leaks
  * wimax/i2400m: fix a memory leak bug
  * ravb: Fix use-after-free ravb_tstamp_skb
  * Tools: hv: kvp: eliminate 'may be used uninitialized' warning
  * IB/mlx4: Fix memory leaks
  * ceph: fix buffer free while holding i_ceph_lock in __ceph_setxattr()
  * KVM: arm/arm64: Only skip MMIO insn once
  * libceph: allow ceph_buffer_put() to receive a NULL ceph_buffer
  * spi: bcm2835aux: ensure interrupts are enabled for shared handler
  * spi: bcm2835aux: unifying code between polling and interrupt driven code
  * spi: bcm2835aux: remove dangerous uncontrolled read of fifo
  * spi: bcm2835aux: fix corruptions for longer spi transfers
  * Revert "x86/apic: Include the LDR when clearing out APIC registers"
  * net: fix skb use after free in netpoll
  * net: stmmac: dwmac-rk: Don't fail if phy regulator is absent
  * Linux 4.4.192

  
     4.4.192 upstream stable release
     from git://git.kernel.org/

To manage notifications about this bug 

[Kernel-packages] [Bug 1845391] Re: SafeSetID LSM should be built but disabled by default

2019-09-25 Thread Tyler Hicks
A pull request for 5.4 included a fix to make SafeSetID useful due to a
bug in 5.3. Details can be read here:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1b5fb415442eb3ec946d48afe8c87b0f2fd42d7c

The needed commit is located here:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21ab8580b383f27b7f59b84ac1699cb26d6c3d69

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

Title:
  SafeSetID LSM should be built but disabled by default

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The SafeSetID LSM is unlikely to be useful, by default, for a general
  purpose OS but a system integrator may want to make use of it in
  certain cases. We should build SafeSetID but not enable it by default
  in Ubuntu. The LSM can be put to use using the lsm= kernel boot
  parameter. For example, lsm=capability,yama,safesetid,apparmor could
  be specified to make use of SafeSetID in addition to the LSMs that we
  use by default in Ubuntu 19.10.

  You can verify that it is enabled by reading the lsm file in
  securityfs:

  $ cat /sys/kernel/security/lsm
  capability,yama,safesetid,apparmor

  Documentation on configuring SafeSetID can be found here:

  https://www.kernel.org/doc/html/latest/admin-guide/LSM/SafeSetID.html

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

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


[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.1 -proposed tracker

2019-09-25 Thread Marcelo Cerri
** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  bionic/linux-aws-fips: 4.15.0-2001.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1844380
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Wednesday, 25. September 2019 21:02 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842804
  variant: debs

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

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


[Kernel-packages] [Bug 1845391] [NEW] SafeSetID LSM should be built but disabled by default

2019-09-25 Thread Tyler Hicks
Public bug reported:

The SafeSetID LSM is unlikely to be useful, by default, for a general
purpose OS but a system integrator may want to make use of it in certain
cases. We should build SafeSetID but not enable it by default in Ubuntu.
The LSM can be put to use using the lsm= kernel boot parameter. For
example, lsm=capability,yama,safesetid,apparmor could be specified to
make use of SafeSetID in addition to the LSMs that we use by default in
Ubuntu 19.10.

You can verify that it is enabled by reading the lsm file in securityfs:

$ cat /sys/kernel/security/lsm
capability,yama,safesetid,apparmor

Documentation on configuring SafeSetID can be found here:

https://www.kernel.org/doc/html/latest/admin-guide/LSM/SafeSetID.html

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Tyler Hicks (tyhicks)
 Status: 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/1845391

Title:
  SafeSetID LSM should be built but disabled by default

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The SafeSetID LSM is unlikely to be useful, by default, for a general
  purpose OS but a system integrator may want to make use of it in
  certain cases. We should build SafeSetID but not enable it by default
  in Ubuntu. The LSM can be put to use using the lsm= kernel boot
  parameter. For example, lsm=capability,yama,safesetid,apparmor could
  be specified to make use of SafeSetID in addition to the LSMs that we
  use by default in Ubuntu 19.10.

  You can verify that it is enabled by reading the lsm file in
  securityfs:

  $ cat /sys/kernel/security/lsm
  capability,yama,safesetid,apparmor

  Documentation on configuring SafeSetID can be found here:

  https://www.kernel.org/doc/html/latest/admin-guide/LSM/SafeSetID.html

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

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


[Kernel-packages] [Bug 1845390] [NEW] Disco update: upstream stable patchset 2019-09-25

2019-09-25 Thread Kamal Mostafa
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2019-09-25

Ported from the following upstream stable releases:
v4.19.74, v5.2.16

   from git://git.kernel.org/

bridge/mdb: remove wrong use of NLM_F_MULTI
cdc_ether: fix rndis support for Mediatek based smartphones
ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()'
isdn/capi: check message length in capi_write()
ixgbe: Fix secpath usage for IPsec TX offload.
net: Fix null de-reference of device refcount
net: gso: Fix skb_segment splat when splitting gso_size mangled skb having 
linear-headed frag_list
net: phylink: Fix flow control resolution
net: sched: fix reordering issues
sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero
sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()'
sctp: use transport pf_retrans in sctp_do_8_2_transport_strike
tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR
tipc: add NULL pointer check before calling kfree_rcu
tun: fix use-after-free when register netdev failed
gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist
gpio: fix line flag validation in linehandle_create
Btrfs: fix assertion failure during fsync and use of stale transaction
ixgbe: Prevent u8 wrapping of ITR value to something less than 10us
genirq: Prevent NULL pointer dereference in resend_irqs()
KVM: s390: kvm_s390_vm_start_migration: check dirty_bitmap before using it as 
target for memset()
KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl
KVM: x86: work around leak of uninitialized stack contents
KVM: nVMX: handle page fault in vmread
x86/purgatory: Change compiler flags from -mcmodel=kernel to -mcmodel=large to 
fix kexec relocation errors
powerpc: Add barrier_nospec to raw_copy_in_user()
drm/meson: Add support for XBGR & ABGR formats
clk: rockchip: Don't yell about bad mmc phases when getting
mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue
PCI: Always allow probing with driver_override
gpio: fix line flag validation in lineevent_create
ubifs: Correctly use tnc_next() in search_dh_cookie()
driver core: Fix use-after-free and double free on glue directory
crypto: talitos - check AES key size
crypto: talitos - fix CTR alg blocksize
crypto: talitos - check data blocksize in ablkcipher.
crypto: talitos - fix ECB algs ivsize
crypto: talitos - Do not modify req->cryptlen on decryption.
crypto: talitos - HMAC SNOOP NO AFEU mode requires SW icv checking.
firmware: ti_sci: Always request response from firmware
drm: panel-orientation-quirks: Add extra quirk table entry for GPD MicroPC
drm/mediatek: mtk_drm_drv.c: Add of_node_put() before goto
Revert "Bluetooth: btusb: driver to enable the usb-wakeup feature"
iio: adc: stm32-dfsdm: fix data type
modules: fix BUG when load module with rodata=n
modules: fix compile error if don't have strict module rwx
platform/x86: pmc_atom: Add CB4063 Beckhoff Automation board to critclk_systems 
DMI table
rsi: fix a double free bug in rsi_91x_deinit()
x86/build: Add -Wnoaddress-of-packed-member to REALMODE_CFLAGS, to silence GCC9 
build warning
ixgbevf: Fix secpath usage for IPsec Tx offload
net: fixed_phy: Add forward declaration for struct gpio_desc;
net: sock_map, fix missing ulp check in sock hash case
Revert "mmc: bcm2835: Terminate timeout work synchronously"
mmc: tmio: Fixup runtime PM management during probe
mmc: tmio: Fixup runtime PM management during remove
drm/i915: Restore relaxed padding (OCL_OOB_SUPPRES_ENABLE) for skl+
ixgbe: fix double clean of Tx descriptors with xdp
mt76: mt76x0e: disable 5GHz band for MT7630E
x86/ima: check EFI SetupMode too
kvm: nVMX: Remove unnecessary sync_roots from handle_invept
KVM: SVM: Fix detection of AMD Errata 1096
UBUNTU: upstream stable to v4.19.74, v5.2.16

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    

[Kernel-packages] [Bug 1845128] Re: disco/linux-gcp: 5.0.0-1019.19 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844362
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Testing
- phase-changed: Tuesday, 24. September 2019 11:25 UTC
+ phase: Signoff
+ phase-changed: Wednesday, 25. September 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1845127
bionic/linux-gke-5.0: bug 1845131
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1019.19 -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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Disco:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1844362
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Signoff
  phase-changed: Wednesday, 25. September 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1845127
bionic/linux-gke-5.0: bug 1845131
  variant: debs

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

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


[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.1 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

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

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

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

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1844380
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Ready for Packaging
- phase-changed: Wednesday, 18. September 2019 13:43 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 25. September 2019 21:02 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842804
  variant: debs

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

Title:
  bionic/linux-aws-fips: 4.15.0-2001.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1844380
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Wednesday, 25. September 2019 21:02 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842804
  variant: debs

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

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


[Kernel-packages] [Bug 1845371] Re: eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 20:41 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 20:41 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  variant: debs

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

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


[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.1 -proposed tracker

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

- bionic/linux-aws-fips:  -proposed tracker
+ bionic/linux-aws-fips: 4.15.0-2001.1 -proposed tracker

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

Title:
  bionic/linux-aws-fips: 4.15.0-2001.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  Invalid

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

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

  -- swm properties --
  kernel-stable-master-bug: 1844380
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Wednesday, 25. September 2019 21:02 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842804
  variant: debs

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

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


[Kernel-packages] [Bug 1845371] Re: eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Packaging
- phase-changed: Wednesday, 25. September 2019 19:21 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 25. September 2019 20:41 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 20:41 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building
  variant: debs

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

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


[Kernel-packages] [Bug 1845383] [NEW] CONFIG_LSM should not specify loadpin since it is not built

2019-09-25 Thread Tyler Hicks
Public bug reported:

[Impact]

While inspecting our kernel configs, I noticed that "loadpin" is present
in the CONFIG_LSM string but CONFIG_SECURITY_LOADPIN is not enabled.
This is harmless but should be cleaned up.

[Test Case]

Ensure that /sys/kernel/security/lsm still contains
"capability,yama,apparmor" after rebooting into the new kernel:

$ cat /sys/kernel/security/lsm 
capability,yama,apparmor

Ensure that the current kernel's config does not specify "loadpin" in
the CONFIG_LSM value:

$ grep CONFIG_LSM= /boot/config-$(uname -r)
CONFIG_LSM="yama,integrity,apparmor"

[Regression Potential]

Low. This just limits the CONFIG_LSM value to only contain LSMs that are
being built.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Low
 Assignee: Tyler Hicks (tyhicks)
 Status: Triaged

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

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  CONFIG_LSM should not specify loadpin since it is not built

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  Triaged

Bug description:
  [Impact]

  While inspecting our kernel configs, I noticed that "loadpin" is
  present in the CONFIG_LSM string but CONFIG_SECURITY_LOADPIN is not
  enabled. This is harmless but should be cleaned up.

  [Test Case]

  Ensure that /sys/kernel/security/lsm still contains
  "capability,yama,apparmor" after rebooting into the new kernel:

  $ cat /sys/kernel/security/lsm 
  capability,yama,apparmor

  Ensure that the current kernel's config does not specify "loadpin" in
  the CONFIG_LSM value:

  $ grep CONFIG_LSM= /boot/config-$(uname -r)
  CONFIG_LSM="yama,integrity,apparmor"

  [Regression Potential]

  Low. This just limits the CONFIG_LSM value to only contain LSMs that
  are being built.

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

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


[Kernel-packages] [Bug 1843873] WifiSyslog.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291275/+files/WifiSyslog.txt

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

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] Lsusb.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1843873/+attachment/5291266/+files/Lsusb.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] CurrentDmesg.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291263/+files/CurrentDmesg.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] ProcInterrupts.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291270/+files/ProcInterrupts.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] RfKill.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1843873/+attachment/5291273/+files/RfKill.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] Lspci.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1843873/+attachment/5291265/+files/Lspci.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] UdevDb.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1843873/+attachment/5291274/+files/UdevDb.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] ProcModules.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291271/+files/ProcModules.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] ProcCpuinfo.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291267/+files/ProcCpuinfo.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] ProcCpuinfoMinimal.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291268/+files/ProcCpuinfoMinimal.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] CRDA.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1843873/+attachment/5291262/+files/CRDA.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] ProcEnviron.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291269/+files/ProcEnviron.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] IwConfig.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291264/+files/IwConfig.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] PulseList.txt

2019-09-25 Thread Simon Poet
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291272/+files/PulseList.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Kernel-packages] [Bug 1843873] Re: Sound distored on Hades Canyon NUC

2019-09-25 Thread Simon Poet
apport information

** Tags added: apport-collected disco

** Description changed:

  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :
  
- https://www.intel.co.uk/content/www/uk/en/products/boards-
- kits/nuc/kits/nuc8i7hvk.html
+ 
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  sparky 1447 F pulseaudio
+  /dev/snd/controlC1:  sparky 1447 F pulseaudio
+  /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-09-25 (0 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ MachineType: Intel(R) Client Systems NUC8i7HVK
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-29-generic N/A
+  linux-backports-modules-5.0.0-29-generic  N/A
+  linux-firmware1.178.3
+ Tags:  disco
+ Uname: Linux 5.0.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/05/2019
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
+ dmi.board.name: NUC8i7HVB
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: J68196-504
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Intel Corporation
+ dmi.chassis.version: 2.0
+ dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
+ dmi.product.family: Intel NUC
+ dmi.product.name: NUC8i7HVK
+ dmi.product.version: J71485-504
+ dmi.sys.vendor: Intel(R) Client Systems

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1843873/+attachment/5291261/+files/AlsaInfo.txt

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

Title:
  Sound distored on Hades Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted 
(unusable). Problem does not occur with a fresh install of Ubuntu 18.10
  Full Specs for the device can be found here :

  
https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sparky 1447 F pulseaudio
   /dev/snd/controlC1:  sparky 1447 F pulseaudio
   /dev/snd/pcmC1D10p:  sparky 1447 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-09-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Intel(R) Client Systems NUC8i7HVK
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646
  dmi.board.name: NUC8i7HVB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J68196-504
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i7HVK
  dmi.product.version: J71485-504
  dmi.sys.vendor: Intel(R) Client Systems

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

-- 
Mailing list: 

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

2019-09-25 Thread Mauricio Faria de Oliveira
** Tags added: sts

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

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

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in debian-installer source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in debian-installer source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in debian-installer source package in Disco:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in debian-installer source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

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

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

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

  [Test Case]

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

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

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

     No regressions observed between the original and test kernels.

  [Regression Potential]

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1845374] [NEW] Xenial update: 4.4.192 upstream stable release

2019-09-25 Thread Connor Kuehl
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:

   4.4.192 upstream stable release
   from git://git.kernel.org/

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

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

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

Title:
  Xenial update: 4.4.192 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  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:

 4.4.192 upstream stable release
 from git://git.kernel.org/

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

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


[Kernel-packages] [Bug 1843644] Re: touchpad not working on LHMZNIY Yepbook

2019-09-25 Thread Quentin Goncalves
I now have those messages when i start ubuntu
3.164137] Couldn't get size: 0x000e
3.164250] MODSIGN: Couldn't get UEFI db list
3.164137] Couldn't get size: 0x000e
3.056278] i2c_hid i2c_SYNA3602:00: HID over i2c has not been provided an int IRQ

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

Title:
  touchpad not working on LHMZNIY Yepbook

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install, but the touchpad isn't showing in the device list at
  all.And it perfectly work on Windows. Device list attached. Works ok
  if you attach a mouse.

  ProblemType: Bug
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 21:40:32 2019
  InstallationDate: Installed on 2019-09-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  quentin1138 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-09-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Insyde Braswell
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic 
root=UUID=f12f1e0c-114b-401a-9a27-af7ccef1c0b6 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.0.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: E115C.intel.C005
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrE115C.intel.C005:bd05/25/2016:svnInsyde:pnBraswell:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1 - Family
  dmi.product.name: Braswell
  dmi.product.sku: Type1 - SKU0
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: Insyde

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

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


[Kernel-packages] [Bug 1845371] Re: eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1845105
+ packages:
+   main: linux-raspi2
+   meta: linux-meta-raspi2
+ phase: Packaging
+ phase-changed: Wednesday, 25. September 2019 19:21 UTC
+ reason:
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

Title:
  eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Packaging
  phase-changed: Wednesday, 25. September 2019 19:21 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1845105] Re: eoan/linux: 5.3.0-13.14 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 24. September 2019 02:46 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  trackers:
bionic/linux-hwe-edge: bug 1844142
eoan/linux-aws: bug 1844138
eoan/linux-azure: bug 1844139
eoan/linux-gcp: bug 1844140
eoan/linux-kvm: bug 1844141
+   eoan/linux-raspi2: bug 1845371
  variant: debs

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 24. September 2019 02:46 UTC
  reason:
promote-to-proposed: Stalled -- another kernel is currently pending in 
Proposed
  trackers:
bionic/linux-hwe-edge: bug 1844142
eoan/linux-aws: bug 1844138
eoan/linux-azure: bug 1844139
eoan/linux-gcp: bug 1844140
eoan/linux-kvm: bug 1844141
eoan/linux-raspi2: bug 1845371
  variant: debs

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

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


[Kernel-packages] [Bug 1845371] [NEW] eoan/linux-raspi2: 5.3.0-1005.6 -proposed tracker

2019-09-25 Thread Seth Forshee
Public bug reported:

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

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

-- swm properties --
kernel-stable-master-bug: 1845105
packages:
  main: linux-raspi2
  meta: linux-meta-raspi2
phase: Packaging
phase-changed: Wednesday, 25. September 2019 19:21 UTC
reason:
  prepare-package: Pending -- package not yet uploaded
  prepare-package-meta: Pending -- package not yet uploaded
variant: debs

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

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

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-raspi2 (Ubuntu)
 Importance: Medium
 Status: Confirmed

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


** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.09.16-1 kernel-sru-derivative-of-1845105

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

** Changed in: linux-raspi2 (Ubuntu)
   Importance: Undecided => Medium

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

** 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 --
+ variant: debs

** Tags added: kernel-sru-cycle-d2019.09.16-1

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ kernel-stable-master-bug: 1845105
  variant: debs

** Tags added: 

[Kernel-packages] [Bug 1845355] Re: Support Hi1620 zip hw accelerator

2019-09-25 Thread dann frazier
** Changed in: linux (Ubuntu Disco)
   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/1845355

Title:
  Support Hi1620 zip hw accelerator

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.

  [Test Case]
  ubuntu@scobee:~$ dmesg | grep zip
  [   29.688222] hisi_zip :75:00.0: enabling device ( -> 0002)
  [   29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002)
  ubuntu@scobee:~$ lspci | grep ZIP
  75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
  b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)

  [Fix]
  263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon 
QM module
  dfed0098ab91f crypto: hisilicon - add hardware SGL support
  62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support
  79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP
  8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip
  72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM
  ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller 
driver
  00ae05db583a7 crypto: hisilicon - fix kbuild warnings
  db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
  5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning
  902f0babf5457 crypto: hisilicon - add missing single_release
  1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q
  b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t
  62a9d9fc7a210 crypto: hisilicon - Fix return value check in 
hisi_zip_acompress()
  bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning

  [Regression Risk]
  This is a new driver which will only load automatically on systems that 
expose a supported PCI device.

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

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


[Kernel-packages] [Bug 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram

2019-09-25 Thread Thadeu Lima de Souza Cascardo
This is due to kernel commit df44b479654f62b478c18ee4d8bc4e9f897a9844
("kobject: return error code if writing /sys/.../uevent fails"), which
has also just recently been backported to bionic.

Cascardo.

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

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

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


[Kernel-packages] [Bug 1844140] Re: eoan/linux-gcp: 5.3.0-1002.2 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 16:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 16:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1845186] WifiSyslog.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291232/+files/WifiSyslog.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU 

[Kernel-packages] [Bug 1845186] Lsusb.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1845186/+attachment/5291224/+files/Lsusb.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU // American 

[Kernel-packages] [Bug 1845186] ProcCpuinfo.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291225/+files/ProcCpuinfo.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1845186] CurrentDmesg.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291221/+files/CurrentDmesg.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1845186] IwConfig.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291222/+files/IwConfig.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU // 

[Kernel-packages] [Bug 1845186] ProcEnviron.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291227/+files/ProcEnviron.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1845186] ProcCpuinfoMinimal.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291226/+files/ProcCpuinfoMinimal.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  

[Kernel-packages] [Bug 1845186] ProcModules.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291229/+files/ProcModules.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1845186] PulseList.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291230/+files/PulseList.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU // 

[Kernel-packages] [Bug 1845186] ProcInterrupts.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1845186/+attachment/5291228/+files/ProcInterrupts.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: 

[Kernel-packages] [Bug 1845186] CRDA.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1845186/+attachment/5291220/+files/CRDA.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU // American 

[Kernel-packages] [Bug 1845186] UdevDb.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1845186/+attachment/5291231/+files/UdevDb.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU // 

[Kernel-packages] [Bug 1845186] Lspci.txt

2019-09-25 Thread Ulli Horlacher
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1845186/+attachment/5291223/+files/Lspci.txt

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  framstag  10502 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  MachineType: FUJITSU ESPRIMO_P956
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.173.9
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.0.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: FUJITSU // American 

[Kernel-packages] [Bug 1845186] Re: nfs Input/output error

2019-09-25 Thread Ulli Horlacher
apport information

** Tags added: apport-collected bionic

** Description changed:

  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).
  
  Example with a Netapp nfs server:
  
  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  
  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr
  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error
  
  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle
  
  (reboot)
  
  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  
  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr
  
  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp
  
  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29
  
  I get no error with kernel 4.15.0-64:
  
  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  
  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr
  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp
  
  
  Also no error occurs when I use the sync nfs mount option:
  
  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr
  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp
  
  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.
  
  On smaller files, there is error:
  
  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)
  
  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp
  
  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp
  
  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!
  
  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  framstag  10502 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.04
+ MachineType: FUJITSU ESPRIMO_P956
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=7e08b486-a587-4d56-8882-4bf4b0e14b7b ro resume=/dev/disk/by-label/swap
+ ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-29-generic N/A
+  linux-backports-modules-5.0.0-29-generic  N/A
+  linux-firmware1.173.9
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 5.0.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 02/19/2016
+ dmi.bios.vendor: FUJITSU // American Megatrends Inc.
+ dmi.bios.version: V5.0.0.11 R1.13.0 for D3402-A1x
+ dmi.board.name: D3402-A1
+ dmi.board.vendor: FUJITSU
+ dmi.board.version: S26361-D3402-A1
+ dmi.chassis.type: 6
+ dmi.chassis.vendor: FUJITSU
+ dmi.chassis.version: C$WX06
+ dmi.modalias: 

[Kernel-packages] [Bug 1845319] Re: writing 'add' to /sys/devices/vio/uevent fails with ENODEV

2019-09-25 Thread Dan Streetman
This bug was uncovered after a behavior change in upstream systemd (udevadm):
https://github.com/systemd/systemd/issues/13652#issuecomment-535129791

** Bug watch added: github.com/systemd/systemd/issues #13652
   https://github.com/systemd/systemd/issues/13652

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

Title:
  writing 'add' to /sys/devices/vio/uevent fails with ENODEV

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [impact]

  The systemd-udev-trigger service calls 'udevadm trigger --type=devices
  --action=add', which writes 'add' to all /sys/devices/ uevent nodes,
  to re-generate their uevents sent to udev.  Until systemd commit
  97afc0351a96e0daa83964df33937967c75c644f, any errors during this
  process were simply logged to debug and ignored, but now udevadm will
  log errors and return failure.

  On ppc64el, the /sys/devices/vio device returns ENODEV when writing
  'add' to its uevent, which causes the udevadm command to return
  failure, which causes the systemd-udev-trigger system service to fail.

  The kernel vio driver should be fixed to not return ENODEV.

  [test case]

  On a ppc64el system, with any systemd containing commit
  97afc0351a96e0daa83964df33937967c75c644f, check the status of the
  systemd-udev-trigger service, to see that it's failed.

  Alternately, again on a ppc64el system, run as root:

  # echo add > /sys/devices/vio/uevent
  -bash: echo: write error: No such device

  [regression potential]

  the potential should be low, as this appears to have always behaved
  this way, at least for a while now.

  [other info]

  the systemd commit that changes udevadm to start failing for this
  error isn't included in any Ubuntu release yet, this is found from
  systemd upstream testing.

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

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


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

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

apport-collect 1845186

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

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic

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

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


[Kernel-packages] [Bug 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram

2019-09-25 Thread Thadeu Lima de Souza Cascardo
This was a false conclusion, as I was executing /sbin/init instead of
/init. The copying works with 100M.

What seems to cause the failure here is udevadm trigger at /lib/debian-
installer/start-udev failing because writing add to
/sys/devices/vio/uevent will fail with ENODEV.

This is because there is a fake parent device for vio, just to make it
look "pretty", dating back to the conversion of vio to 2.6 driver model
back in 2004. Removing such a bogus device should fix things. I just
don't know yet why this has started to be a problem when it wasn't on
previous releases.

Cascardo.

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

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

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


[Kernel-packages] [Bug 1845186] Re: nfs Input/output error

2019-09-25 Thread Ulli Horlacher
** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1845186

Title:
  nfs Input/output error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Obuntu 18.04 with Linux kernel 5.0.0-29 (and 5.0.0-27) I am getting
  errors when writing files > 200 MB on a nfs filesystem, no matter which
  nfs server I use (Linux or Netapp).

  Example with a Netapp nfs server:

  root@tux:# uname -a
  Linux tux 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  l: dd.tmp - Input/output error

  root@tux:/nfs/rusnas/scr# l
  l: cannot read ./ : Stale file handle

  (reboot)

  root@tux:~# uname -a
  Linux tux 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  root@tux:~# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  
  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 647,364,608 2019-09-24 11:54 dd.tmp

  The same error occurs when I use a Ubuntu 18.04 nfs server with kernel
  5.0.0-29

  I get no error with kernel 4.15.0-64:

  root@tux:# uname -a
  Linux tux 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  root@tux:# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.40337 s, 114 MB/s
  -RW- 1,073,741,824 2019-09-24 11:48 dd.tmp

  
  Also no error occurs when I use the sync nfs mount option:

  root@tux:/# mount.nfs -o
  nfsvers=3,rw,rsize=1048576,wsize=1048576,tcp,timeo=10,soft,sync
  nfs4sas.storage.tik.uni-stuttgart.de:/nfs4sas_scratch /nfs/rusnas/scr

  root@tux:/nfs/rusnas/scr# dd status=progress bs=1M count=1024 if=/dev/zero 
of=dd.tmp; l dd.tmp
  996147200 bytes (996 MB, 950 MiB) copied, 13 s, 76.6 MB/s
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB, 1.0 GiB) copied, 13.7691 s, 78.0 MB/s
  -RW- 1,073,741,824 2019-09-24 11:58 dd.tmp

  As you can see: no more errors, but much slower!
  So, this is not a solution, just a workaround.

  On smaller files, there is error:

  root@diaspora:/nfs/rusnas/software# mount | grep $PWD
  nfs4sas:/nfs4sas_software on /nfs/rusnas/software type nfs 
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,mountaddr=129.69.2.23,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=129.69.2.23)

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=200 if=/dev/zero 
of=dd.tmp; l dd.tmp
  200+0 records in
  200+0 records out
  209715200 bytes (210 MB, 200 MiB) copied, 2.25616 s, 93.0 MB/s
  -RW- 209,715,200 2019-09-24 12:33 dd.tmp

  root@diaspora:/nfs/rusnas/software# dd bs=1M count=300 if=/dev/zero 
of=dd.tmp; l dd.tmp
  dd: closing output file 'dd.tmp': Input/output error
  -RW- 293,535,744 2019-09-24 12:34 dd.tmp

  
  ==> the nfs client in Ubuntu 18.04 kernel 5.0.0 has a bug!

  root@tux:/nfs/rusnas/scr# dpkg -S /boot/vmlinuz-5.0.0-29-generic
  linux-image-5.0.0-29-generic: /boot/vmlinuz-5.0.0-29-generic

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

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


[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2019-09-25 Thread Thorsten
but is there any update on this issue?

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1844140] Re: eoan/linux-gcp: 5.3.0-1002.2 -proposed tracker

2019-09-25 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 16:31 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:building,meta:queued,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  variant: debs

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

Title:
  eoan/linux-gcp: 5.3.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Eoan:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1845105
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 25. September 2019 16:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1845355] [NEW] Support Hi1620 zip hw accelerator

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

[Impact]
The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.

[Test Case]
ubuntu@scobee:~$ dmesg | grep zip
[   29.688222] hisi_zip :75:00.0: enabling device ( -> 0002)
[   29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002)
ubuntu@scobee:~$ lspci | grep ZIP
75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)

[Fix]
263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon QM 
module
dfed0098ab91f crypto: hisilicon - add hardware SGL support
62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support
79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP
8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip
72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM
ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller 
driver
00ae05db583a7 crypto: hisilicon - fix kbuild warnings
db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning
902f0babf5457 crypto: hisilicon - add missing single_release
1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q
b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t
62a9d9fc7a210 crypto: hisilicon - Fix return value check in hisi_zip_acompress()
bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning

[Regression Risk]
This is a new driver which will only load automatically on systems that expose 
a supported PCI device.

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

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

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

** Description changed:

  [Impact]
- The Hi1620 SoC has an onboard zip accelerator that is currently not supported 
by Ubuntu.
+ The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.
  
  [Test Case]
  ubuntu@scobee:~$ dmesg | grep zip
  [   29.688222] hisi_zip :75:00.0: enabling device ( -> 0002)
  [   29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002)
  ubuntu@scobee:~$ lspci | grep ZIP
  75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
  b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
  
  [Fix]
  263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon 
QM module
  dfed0098ab91f crypto: hisilicon - add hardware SGL support
  62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support
  79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP
  8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip
  72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM
  ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller 
driver
  00ae05db583a7 crypto: hisilicon - fix kbuild warnings
  db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
  5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning
  902f0babf5457 crypto: hisilicon - add missing single_release
  1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q
  b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t
  62a9d9fc7a210 crypto: hisilicon - Fix return value check in 
hisi_zip_acompress()
  bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning
  
  [Regression Risk]
  This is a new driver which will only load automatically on systems that 
expose a supported PCI device.

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Disco)
   Status: Triaged => 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/1845355

Title:
  Support Hi1620 zip hw accelerator

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.

  [Test Case]
  ubuntu@scobee:~$ 

  1   2   >