[Kernel-packages] [Bug 1802785] Re: linux-aws: 4.4.0-1073.83 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1802776
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1802776
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

Re: [Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Robert Dinse]

I gave up on it every being fixed and bought some broadcom interfaces
for my machines.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Fri, 23 Nov 2018, Emlyn Bolton wrote:

> Date: Fri, 23 Nov 2018 17:37:46 -
> From: Emlyn Bolton <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
> 
> I'm still seeing this issue on the 4.15.0-39-generic kernel:
>
> [467738.375137] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f70ff8>
>  next_to_watch.status <0>
> [467740.391180] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f711f0>
>  next_to_watch.status <0>
> [467742.407313] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f713e8>
>  next_to_watch.status <0>
> [467744.423373] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
>  Tx Queue <0>
>  TDH  <44>
>  TDT  <44>
>  next_to_use  <44>
>  next_to_clean<25>
>buffer_info[next_to_clean]
>  time_stamp   <106f70e55>
>  next_to_watch<26>
>  jiffies  <106f715e0>
>  next_to_watch.status <0>
> [467745.319133] e1000 :05:01.0 enp5s1f0: Reset adapter
>
> 05:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (Copper) (rev 03)
>   Subsystem: Intel Corporation PRO/1000 MT Dual Port Server Adapter
>   Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
>   Memory at f722 (64-bit, non-prefetchable) [size=128K]
>   Memory at f71c (64-bit, non-prefetchable) [size=256K]
>   I/O ports at d040 [size=64]
>   Expansion ROM at f718 [disabled] [size=256K]
>   Capabilities: [dc] Power Management version 2
>   Capabilities: [e4] PCI-X non-bridge device
>   Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
>   Kernel driver in use: e1000
>   Kernel modules: e1000
>
> 05:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
> Controller (Copper) (rev 03)
>   Subsystem: Intel Corporation PRO/1000 MT Dual Port Server Adapter
>   Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
>   Memory at f720 (64-bit, non-prefetchable) [size=128K]
>   Memory at f714 (64-bit, non-prefetchable) [size=256K]
>   I/O ports at d000 [size=64]
>   Expansion ROM at f710 [disabled] [size=256K]
>   Capabilities: [dc] Power Management version 2
>   Capabilities: [e4] PCI-X non-bridge device
>   Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
>   Kernel driver in use: e1000
>   Kernel modules: e1000
>
>
> This is a dual-port adapter, but I also saw the issue with the on-board i217 
> chip too.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
>  Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
>  Expired
> Status in linux source package in Bionic:
>  Expired
>
> Bug description:
>   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
> hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
> motherboard, controller specifications:
>  Intel® I218V, 1 x Gigabit LAN Controller(s)
>  Intel® I211-AT, 1 x Gigabit LAN
>  Dual Gigabit LAN controller

[Kernel-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load

[maravento]

Bug Confirm in Ubuntu Mate 18.04.1 x64 kernel 4.15.0-39-generic (work
around doesn't work)

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

Title:
  update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware
  fails to load

Status in initramfs-tools:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  This firmware was optional when the MODULE_FIRMWARE statements were
  removed in bug 1626740 by Bionic commit dc0f16f9b50.  The firmware is now
  available and in use, so these statements need to be added back.

  Without these statements, The i915 Kabylake GuC firmware is failing to load
  on boot, and generating dmesg errors.

  == Fix ==
  Revert Bionic commit dc0f16f9b5084e6be2b8c79f8c6cd499a3451791.

  == Regression Potential ==
  Low.  Adding a statement back that was removed by a SAUCE patch.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  == Original Bug Report ==
  The i915 Kabylake GuC firmware is failing to load on boot, and generating 
dmesg errors.  The Kabylake HuC firmware succeeds.  All files exist.  I've also 
verified the Kabylake GuC firmware matches the correct file size and md5 listed 
on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Key

[Kernel-packages] [Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).

[Dima]

The main bug report is here https://bugs.freedesktop.org/show_bug.cgi?id=93782
I've tried video=SVIDEO-1:d as boot parameter on 18.04 live CD and it helps. It 
turns off TV out and the booting is fast as it should. Thank you all for your 
time and attention.

** Bug watch added: freedesktop.org Bugzilla #93782
   https://bugs.freedesktop.org/show_bug.cgi?id=93782

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

Title:
  The booting is too long with drm_atomic_helper_wait_for_dependencies
  errors (xenial+hwe,bionic).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1,2) Please see the apport attachments
  3) Fast booting without errors as with xenial non-hwe kernels
  4) The booting is too long
  The errors are similar to this:

  [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* 
[CRTC:41:pipe B] flip_done timed out
  [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* 
[PLANE:35:plane B] flip_done timed out

  The errors appears on Toshiba Satellite L300-11Q.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: LXDE
  Date: Fri Aug  3 20:34:23 2018
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-20-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1707 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9430 irq 26'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,1179ff64,0013 
HDA:11c11040,11790001,00100200'
 Controls  : 20
 Simple ctrls  : 9
  CasperVersion: 1.394
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: TOSHIBA Satellite L300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=ru 
keyboard-configuration/layoutcode?=ru
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-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/10/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite L300
  dmi.product.version: PSLB0E-014012RU
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

[Guilherme G. Piccoli]

** Attachment added: "lp1797990_verification.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5215743/+files/lp1797990_verification.tgz

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * A kexec/crash kernel might get stuck and fail to boot
     (for crash kernel, kdump fails to collect a crashdump)
     if a PCI device is buggy/stuck/looping and triggers a
     continuous flood of MSI(X) interrupts (that the kernel
     does not yet know about).

   * This fix allowed to obtain crashdumps when debugging a
     heavy-load scenario, in which a (heavy-loaded) network
     adapter wouldn't stop triggering MSI-X interrupts ever
     after panic()->kdump kicked in.

   * This fix disables MSI(X) in all PCI devices on early
     boot (this is OK as it's (re-)enabled normally later)
     with a kernel cmdline parameter (disabled by default).

  [Test Case]

   * A synthetic test-case is not yet available, however,
     this particular system/workload triggered the problem
     consistently, and it was used for development/testing.

   * We'll update this bug once a synthetic test-case is
     available; we're working on patching QEMU for this.

   * $ cat /proc/cmdline
 <...> pci=clearmsi

 $ dmesg | grep 'Clearing MSI'
     [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk)

   * The comparison of 'dmesg -t | sort' has been reviewed
     between option disabled/enabled on boot & kexec modes,
     and only expected differences found (MHz, PIDs, MIPS).

  [Regression Potential]

   * The potential area for regressions is early boot,
     particularly effects of applying quirks during PCI
     bus scan, which is changed/broader w/ these patches.

   * However, all quirks are applied based on PCI ID
     matching, so would only apply if actually targeting
     a new device.

   * Moreover, the new quirk is only applied based on
     a kernel cmdline parameter that is disabled by
     default, which constraints even more when this
     is actually in effect.

  [Other Info]

   * The patch series is still under review/discussion
     upstream, but it's relatively important for Ubuntu
     users at this point, and after internal discussions
     we decided to submit it for SRU.

   * These are links to the linux-pci archive with the
     patches [1, 2, 3]

     [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks
     
https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/

     [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code
     
https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/

     [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot
     
https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/

  [Original Description]

  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

[Guilherme G. Piccoli]

Thanks Maurício for submitting the patches and taking care of the bug
while I was out.

I've verified all the 3 releases (in fact, I've also verified Trusty HWE) with 
a similar
test as used by Maurício, "dmesg -t | sort" and the kernels are running fine.
During kdump, with the "pci=clearmsi" option, we can see the message:

"Clearing MSI/MSI-X enable bits early in boot (quirk)"
which shows that the quirk is working.

I'll attach the logs for documentation purposes.
Cheers,


Guilherme

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

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

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * A kexec/crash kernel might get stuck and fail to boot
     (for crash kernel, kdump fails to collect a crashdump)
     if a PCI device is buggy/stuck/looping and triggers a
     continuous flood of MSI(X) interrupts (that the kernel
     does not yet know about).

   * This fix allowed to obtain crashdumps when debugging a
     heavy-load scenario, in which a (heavy-loaded) network
     adapter wouldn't stop triggering MSI-X interrupts ever
     after panic()->kdump kicked in.

   * This fix disables MSI(X) in all PCI devices on early
     boot (this is OK as it's (re-)enabled normally later)
     with a kernel cmdline parameter (disabled by default).

  [Test Case]

   * A synthetic test-case is not yet available, however,
     this particular system/workload triggered the problem
     consistently, and it was used for development/testing.

   * We'll update this bug once a synthetic test-case is
     available; we're working on patching QEMU for this.

   * $ cat /proc/cmdline
 <...> pci=clearmsi

 $ dmesg | grep 'Clearing MSI'
     [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk)

   * The comparison of 'dmesg -t | sort' has been reviewed
     between option disabled/enabled on boot & kexec modes,
     and only expected differences found (MHz, PIDs, MIPS).

  [Regression Potential]

   * The potential area for regressions is early boot,
     particularly effects of applying quirks during PCI
     bus scan, which is changed/broader w/ these patches.

   * However, all quirks are applied based on PCI ID
     matching, so would only apply if actually targeting
     a new device.

   * Moreover, the new quirk is only applied based on
     a kernel cmdline parameter that is disabled by
     default, which constraints even more when this
     is actually in effect.

  [Other Info]

   * The patch series is still under review/discussion
     upstream, but it's relatively important for Ubuntu
     users at this point, and after internal discussions
     we decided to submit it for SRU.

   * These are links to the linux-pci archive with the
     patches [1, 2, 3]

     [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks
     
https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/

     [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code
     
https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/

     [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot
     
https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/

  [Original Description]

  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

To manage notifications

[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

[Emlyn Bolton]

I'm still seeing this issue on the 4.15.0-39-generic kernel:

[467738.375137] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
  Tx Queue <0>
  TDH  <44>
  TDT  <44>
  next_to_use  <44>
  next_to_clean<25>
buffer_info[next_to_clean]
  time_stamp   <106f70e55>
  next_to_watch<26>
  jiffies  <106f70ff8>
  next_to_watch.status <0>
[467740.391180] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
  Tx Queue <0>
  TDH  <44>
  TDT  <44>
  next_to_use  <44>
  next_to_clean<25>
buffer_info[next_to_clean]
  time_stamp   <106f70e55>
  next_to_watch<26>
  jiffies  <106f711f0>
  next_to_watch.status <0>
[467742.407313] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
  Tx Queue <0>
  TDH  <44>
  TDT  <44>
  next_to_use  <44>
  next_to_clean<25>
buffer_info[next_to_clean]
  time_stamp   <106f70e55>
  next_to_watch<26>
  jiffies  <106f713e8>
  next_to_watch.status <0>
[467744.423373] e1000 :05:01.0 enp5s1f0: Detected Tx Unit Hang
  Tx Queue <0>
  TDH  <44>
  TDT  <44>
  next_to_use  <44>
  next_to_clean<25>
buffer_info[next_to_clean]
  time_stamp   <106f70e55>
  next_to_watch<26>
  jiffies  <106f715e0>
  next_to_watch.status <0>
[467745.319133] e1000 :05:01.0 enp5s1f0: Reset adapter

05:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
Controller (Copper) (rev 03)
Subsystem: Intel Corporation PRO/1000 MT Dual Port Server Adapter
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
Memory at f722 (64-bit, non-prefetchable) [size=128K]
Memory at f71c (64-bit, non-prefetchable) [size=256K]
I/O ports at d040 [size=64]
Expansion ROM at f718 [disabled] [size=256K]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device
Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
Kernel driver in use: e1000
Kernel modules: e1000

05:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet 
Controller (Copper) (rev 03)
Subsystem: Intel Corporation PRO/1000 MT Dual Port Server Adapter
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
Memory at f720 (64-bit, non-prefetchable) [size=128K]
Memory at f714 (64-bit, non-prefetchable) [size=256K]
I/O ports at d000 [size=64]
Expansion ROM at f710 [disabled] [size=256K]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device
Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
Kernel driver in use: e1000
Kernel modules: e1000


This is a dual-port adapter, but I also saw the issue with the on-board i217 
chip too.

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

Title:
  Ethernet E1000 Controller Hangs

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  Expired

Bug description:
   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
motherboard, controller specifications:
  Intel® I218V, 1 x Gigabit LAN Controller(s)
  Intel® I211-AT, 1 x Gigabit LAN
  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
appliance
  Support Teaming Technology
  ASUS Turbo LAN Utility
  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
  This machine has a number of Qemu/KVM virtual guests and is using a software 
bridge to share the interface.
  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
multiple machines here.
  Here are the messages from dmesg:
  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

[whl2]

Apparently, fans go 100% on Ubuntu 18.04 even with 4.4.0-21-generic kernel.
I'm out of ideas...

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1803827] Re: Cant install from usb or normal upgrade(says not supported) (Eee PC 904HD)

[jonh]

** Summary changed:

- Cant install from usb or normal upgrade(says not supported)
+ Cant install from usb or normal upgrade(says not supported) (Eee PC 904HD)

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

Title:
  Cant install from usb or normal upgrade(says not supported) (Eee PC
  904HD)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Cant install lubuntu 32 bit 18.10 or 19.04 (Disco Dingo Daily Builds) from 
usb or normal upgrade from 18.04 to 18.10(says not supported) it displays 
cdrom/casper/filesystem.squashfs error for the Asus Eee PC 904HD
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-39-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asus725 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 24'
     Mixer name : 'Realtek ALC269'
     Components : 'HDA:10ec0269,1043834a,0014'
     Controls  : 22
     Simple ctrls  : 10
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 18.04
  MachineType: ASUSTeK Computer INC. 904HD
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=d88102d1-73dc-40ae-9e3b-8d09460b1ae5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic i686
  UpgradeStatus: Upgraded to bionic on 2018-11-16 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 904HD
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd09/22/2008:svnASUSTeKComputerINC.:pn904HD:pvrx.x:rvnASUSTeKComputerINC.:rn904HD:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 904HD
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Kernel-packages] [Bug 1802665] Re: No Restart Shutdown or Suspend (Aspire 5516)

[jonh]

** Summary changed:

- No Restart Shutdown or Suspend
+ No Restart Shutdown or Suspend (Aspire 5516)

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

Title:
  No Restart Shutdown or Suspend (Aspire 5516)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Reason is i changed cpu from tf 20 to turion 64 tl 68 for acer aspire
  5516  plus when i try to install 18.10 from usb it fails and displays
  cdrom/casper/filesystem.squashfs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer   1847 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sat Nov 10 12:41:18 2018
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5516
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=435bbf22-b287-40fd-ae42-298df9db9a13 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-11-09 (0 days ago)
  dmi.bios.date: 04/21/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.10
  dmi.board.name: Aspire 5516
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV1.10:bd04/21/2009:svnAcer:pnAspire5516:pvrV1.10:rvnAcer:rnAspire5516:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5516
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1802646] Re: no shutdown, reboot, suspent because i changed cpu from tf 20 to turion 68 (Aspire 5516)

[jonh]

** Summary changed:

- no shutdown,reboot,suspent because i changed cpu from tf 20 to turion 68
+ no shutdown,reboot,suspent because i changed cpu from tf 20 to turion 68 
(Aspire 5516)

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

Title:
  no shutdown,reboot,suspent because i changed cpu from tf 20 to turion
  68 (Aspire 5516)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  nothing is crashing its just doesn't shutdown reboot or sleep(wakes up
  1 second after it sleeps) for the day a change cpu from AMD Athlon 64
  TF-20 to AMD Turion 64 X2 TL-68 for the Acer Aspire 5516 and 18.10
  lubuntu cant install from usb live cdrom/casper/filesystem.squashfs
  error something for Acer Aspire 5516

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-38-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer845 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf040 irq 16'
     Mixer name : 'Realtek ALC272X'
     Components : 'HDA:10ec0272,10250213,0011'
     Controls  : 21
     Simple ctrls  : 10
  CurrentDesktop: LXDE
  Date: Sat Nov 10 15:32:05 2018
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5516
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=f16d84dc-e5a8-481f-8baa-2f06e289b595 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.10
  dmi.board.name: Aspire 5516
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV1.10:bd04/21/2009:svnAcer:pnAspire5516:pvrV1.10:rvnAcer:rnAspire5516:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5516
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1803692] Re: bionic 4.15 nvme regression from trusty 4.4 with two identical devices

[James Dingwall]

I have changed the bug to 'invalid' as I do not expect a fix in Ubuntu
for the firmware bug.

https://downloadcenter.intel.com/download/28320/Known-Issue-Intel-SSD-
760p-Pro-7600p-Series-SubNQN-Conflict-on-Linux

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

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

Title:
  bionic 4.15 nvme regression from trusty 4.4 with two identical devices

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have a system containing two identical nvme devices.  When booting a
  trusty PXE image with kernel 4.4.0-38-generic both devices are
  detected and available:

  # nvme id-ctrl /dev/nvme0
  NVME Identify Controller:
  vid : 0x8086
  ssvid   : 0x8086
  sn  : BTHH82250N1X1P0E
  mn  : INTEL SSDPEKKF010T8L
  fr  : L08P
  ...

  # nvme id-ctrl /dev/nvme1
  NVME Identify Controller:
  vid : 0x8086
  ssvid   : 0x8086
  sn  : BTHH82250N261P0E
  mn  : INTEL SSDPEKKF010T8L
  fr  : L08P
  ...

  
  # dmesg | grep nvme
  [5.106516]  nvme0n1: p1 p2 p3 p4
  [5.106615]  nvme1n1: p1 p2


  After booting a bionic PXE image based on 4.15.0-38-generic only the
  first nvme device is enabled, the second is detected but disabled as
  both devices have the same nqn:

  nvme nvme1: ignoring ctrl due to duplicate subnqn 
(nqn.2017-12.org.nvmeexpress:uuid:----).
  nvme nvme1: Removing after probe failure status: -22

  
  The nqn string is found in the device firmware rather than being generated by 
Linux but there does not seem to be an operation in nvme-cli to change this.  
(It is also questionable if the device firmware value is correct according to 
section 7.9 of 
https://nvmexpress.org/wp-content/uploads/NVM-Express-1_3a-20171024_ratified.pdf.
  My reading of the specification is that the string should start 
nqn.2014-08.org.nvmeexpress:uuid: with a random UUID, and I assume a random 
UUID per device.)

  The Windows 10 installation provided on the system did not have any
  problems operating with both devices.

  Looking at the kernel nvme driver history suggests that in 4.4 it
  didn't care or validate the nqn but now it does there is a problem.

  Our typical installation is a zpool mirror across two devices and this
  is preventing us moving from trusty to bionic.

  This is a report of a similar issue:
  https://ask.fedoraproject.org/en/question/128422/one-of-two-
  identical-m2-nvme-drives-disabling-due-to-same-nqn/

  It may be worth noting that if the nvme device does not provide an nqn then 
it seems one is generated based on the device serial number so a system with 
two Samsung MZVLB256HAHQ devices works fine.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3440 F pulseaudio
  CasperVersion: 1.340.2
  CurrentDmesg: [  151.172010] init: plymouth-stop pre-start process (4137) 
terminated with status 1
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  LiveMediaBuild: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 89e5:1001  
   Bus 001 Device 002: ID 17ef:6099 Lenovo 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 30C8S04Y00
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: us1931.efi root=/dev/nfs boot=casper netboot=nfs 
nfsroot=192.168.10.150:/srv/boot/us1931 locale=en_GB.UTF-8 keyb=gb 
mirror/country=GB ip=dhcp zinstall= BOOTIF=01-30-9c-23-cb-2a-46 toram
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1VKT1BA
  dmi.board.name: 3138
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305152508085
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1VKT1BA:bd08/17/2018:svnLENOVO:pn30C8S04Y00:pvrThinkStationP330:rvnLENOVO:rn3138:rvrSDK0J40697WIN3305152508085:

[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

[Dariusz Gadomski]

Alright, thanks Seb. It makes it verified then.

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

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

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  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-firmware/+bug/1804841/+subscriptions

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

[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

[Sebastien Bacher]

@Dariusz, I guess we would think about that but I wouldn't block the SRU
on that since the change isn't buggy even without hwdata, you get a
label with a vendor code instead of a buggy value, which is still an
improvement.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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

[Kernel-packages] [Bug 1803692] Re: bionic 4.15 nvme regression from trusty 4.4 with two identical devices

[James Dingwall]

The linked thread on fedoraproject.org indicates that a firmware update
for the device will be necessary to resolve 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/1803692

Title:
  bionic 4.15 nvme regression from trusty 4.4 with two identical devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a system containing two identical nvme devices.  When booting a
  trusty PXE image with kernel 4.4.0-38-generic both devices are
  detected and available:

  # nvme id-ctrl /dev/nvme0
  NVME Identify Controller:
  vid : 0x8086
  ssvid   : 0x8086
  sn  : BTHH82250N1X1P0E
  mn  : INTEL SSDPEKKF010T8L
  fr  : L08P
  ...

  # nvme id-ctrl /dev/nvme1
  NVME Identify Controller:
  vid : 0x8086
  ssvid   : 0x8086
  sn  : BTHH82250N261P0E
  mn  : INTEL SSDPEKKF010T8L
  fr  : L08P
  ...

  
  # dmesg | grep nvme
  [5.106516]  nvme0n1: p1 p2 p3 p4
  [5.106615]  nvme1n1: p1 p2


  After booting a bionic PXE image based on 4.15.0-38-generic only the
  first nvme device is enabled, the second is detected but disabled as
  both devices have the same nqn:

  nvme nvme1: ignoring ctrl due to duplicate subnqn 
(nqn.2017-12.org.nvmeexpress:uuid:----).
  nvme nvme1: Removing after probe failure status: -22

  
  The nqn string is found in the device firmware rather than being generated by 
Linux but there does not seem to be an operation in nvme-cli to change this.  
(It is also questionable if the device firmware value is correct according to 
section 7.9 of 
https://nvmexpress.org/wp-content/uploads/NVM-Express-1_3a-20171024_ratified.pdf.
  My reading of the specification is that the string should start 
nqn.2014-08.org.nvmeexpress:uuid: with a random UUID, and I assume a random 
UUID per device.)

  The Windows 10 installation provided on the system did not have any
  problems operating with both devices.

  Looking at the kernel nvme driver history suggests that in 4.4 it
  didn't care or validate the nqn but now it does there is a problem.

  Our typical installation is a zpool mirror across two devices and this
  is preventing us moving from trusty to bionic.

  This is a report of a similar issue:
  https://ask.fedoraproject.org/en/question/128422/one-of-two-
  identical-m2-nvme-drives-disabling-due-to-same-nqn/

  It may be worth noting that if the nvme device does not provide an nqn then 
it seems one is generated based on the device serial number so a system with 
two Samsung MZVLB256HAHQ devices works fine.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3440 F pulseaudio
  CasperVersion: 1.340.2
  CurrentDmesg: [  151.172010] init: plymouth-stop pre-start process (4137) 
terminated with status 1
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  LiveMediaBuild: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 89e5:1001  
   Bus 001 Device 002: ID 17ef:6099 Lenovo 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 30C8S04Y00
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: us1931.efi root=/dev/nfs boot=casper netboot=nfs 
nfsroot=192.168.10.150:/srv/boot/us1931 locale=en_GB.UTF-8 keyb=gb 
mirror/country=GB ip=dhcp zinstall= BOOTIF=01-30-9c-23-cb-2a-46 toram
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1VKT1BA
  dmi.board.name: 3138
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305152508085
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1VKT1BA:bd08/17/2018:svnLENOVO:pn30C8S04Y00:pvrThinkStationP330:rvnLENOVO:rn3138:rvrSDK0J40697WIN3305152508085:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 30C8S04Y00
  dmi.product.version: ThinkStation P330
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  A

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-11-23 10:29 EDT---
IBM Bugzilla status-> closed, won't fix be Canonical.

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

Title:
  [18.04] include support for Python bindings in "perf"

Status in The Ubuntu-power-systems project:
  Won't Fix
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Invalid

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215696/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215698/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04

[Konstantinos Kontodimas]

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215685/+files/AlsaInfo.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215686/+files/CRDA.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215688/+files/IwConfig.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215689/+files/Lspci.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215687/+files/CurrentDmesg.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215690/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215691/+files/ProcCpuinfo.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215692/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215693/+files/ProcEnviron.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215694/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215695/+files/ProcModules.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215696/+files/PulseList.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215697/+files/UdevDb.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564463/+attachment/5215698/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

[Tuomas]

I have the same issue with Dell TB18DC tb dock and Dell Precision 7530
laptop. Using ukuu mainline kernel 4.19.4-041904-generic. I think latest
system bios update 1.4.2 (https://www.dell.com/support/home/us/en/04
/product-support/product/precision-15-7530-laptop/drivers) made this
problem appear a lot more often than earlier.

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

Title:
  USB over thunderbolt turns off every once in a while

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

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd :0e:00.0: remove, state 1

   
  [279389.814110] usb usb3: USB disconnect, device number 1 

   
  [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered 

   
  [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller   

   
  [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus 
number 3
 
  [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 
0x100 quirks 0x1410 

  [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 

   
  [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1  
 
  [279389.949982] usb usb3: Product: xHCI Host Controller   

   
  [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd  

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1564463/+attachment/5215697/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1804841] [NEW] iwlwifi Microcode SW error detected. Restarting 0x2000000.

[UrkoM]

Public bug reported:

This seems to be a return of an existing bug, in newer hardware and
microcode versions.

Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
Firmware version: 34.0.1
Description:Ubuntu 18.04.1 LTS

Frequent errors as soon as I connect to wifi:
Microcode SW error detected.  Restarting 0x200.

Expected to happen: Great and stable wifi like a couple of weeks ago
What happens: very slow, intermittent internet access, lots of ping loss

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Nov 23 15:23:54 2018
Dependencies:
 
InstallationDate: Installed on 2018-09-03 (81 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  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-firmware/+bug/1804841/+subscriptions

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215695/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

[UrkoM]

** Description changed:

  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.
  
  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS
  
  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.
  
  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss
  
+ Found a suggestion of a workaround: adding these lines to
+ /etc/NetworkManager/NetworkManager.conf
+ 
+ [device]
+ wifi.scan-rand-mac-address=no
+ 
+ These lines were already there, not added by me.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  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-firmware/+bug/1804841/+subscriptions

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215688/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1564463/+attachment/5215689/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215694/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1564463] AlsaInfo.txt

[Konstantinos Kontodimas]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215685/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215691/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1564463/+attachment/5215690/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215692/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215687/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1564463/+attachment/5215686/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

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

[Konstantinos Kontodimas]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1564463/+attachment/5215693/+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/1564463

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1564463] Re: Joystick Dragonrise Axes confused in Ubuntu 14.04

[Konstantinos Kontodimas]

ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kontodimas   4337 F pulseaudio
 /dev/snd/pcmC1D0c:   kontodimas   4337 F...m pulseaudio
 /dev/snd/pcmC1D0p:   kontodimas   4337 F...m pulseaudio
 /dev/snd/controlC0:  kontodimas   4337 F pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a950d5f9-3d5c-4cbf-ad0f-98f205f11cb9
InstallationDate: Installed on 2014-04-14 (1683 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.2)
MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=d479d51e-867d-4dd5-bc7b-b0ee85d0d7fa ro quiet splash 
nvidia-drm.modeset=1 noapic crashkernel=512M-:192M vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-11-generic N/A
 linux-backports-modules-4.18.0-11-generic  N/A
 linux-firmware 1.175.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags:  cosmic
Uname: Linux 4.18.0-11-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-11-02 (20 days ago)
UserGroups: adm bumblebee cdrom dialout dip libvirt libvirtd lpadmin plugdev 
sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 03/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.71
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2166
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.42
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.sku: F7R44EA#AB7
dmi.product.version: 098B1140410620180
dmi.sys.vendor: Hewlett-Packard


** Tags added: apport-collected cosmic

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

Title:
  Joystick Dragonrise Axes confused in Ubuntu 14.04

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

Bug description:
  In Ubuntu 14.04 axis 2 (left-right of the right joystick) is hardly
  working.

  Its conflicting and superimposed by axis 0 (left-right of the left
  joystick)

  Axis 2 was allready behaving bad in eralier versions now its completly
  broken.

  Also jscal complains when applying stored settings from earlier ubuntu
  versions as the joystick now has 6 axes [0-5] and used to have 7, but
  this seems correct.

  The Dragonrise chip seems to be very widespread among different
  speedlink and LinQ models

  There is a related bugreport in Debian Bug-Tracker: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785606
  that makes

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

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

[Kernel-packages] [Bug 1803179] Re: System does not reliably come out of suspend

[Mathieu Trudel-Lapierre]

Seems like this is caused by nvidia drivers not liking s2idle or forcing
the use of 'deep' leads to reliable suspend/resume cycles. Properly
removing nvidia drivers leads to a working system.

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

Title:
  System does not reliably come out of suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 (9750); it might eventually manage to suspend when the lid
  is closed, but more often than not will not wake up again when the lid
  is opened. Waking up using the power button often results in a system
  that is apparently frozen (graphics displayed are the last on screen
  before suspend, clock seconds do not change)

  System is unresponsive to the keyboard at that time (can't switch to a
  VT or otherwise interact with the system other than holding the power
  button for a few seconds to shut it down).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtrudel2516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 10:42:08 2018
  InstallationDate: Installed on 2018-11-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1685442]

[Ville-syrjala-e]

*** Bug 108747 has been marked as a duplicate of this bug. ***

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1685442]

[R-tom-6]

(In reply to Ville Syrjala from comment #78)
> Fixes posted:
> https://patchwork.freedesktop.org/series/52378/

Likewise, building the `tvout_fixes` branch results in a kernel that
fixes the issue on my MacBook, which is a great result! As a complete
outsider to the DRI/DRM process, how does this then get moved into the
mainline kernel?

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[ALinuxUser]

@Thorsten

My config: NFC; new BIOS; i2c_i801 unblacklisted; 4.19 kernel; firmware
up to date (I think; the Windows only nature of some of the updates
makes its hard to tell); synaptics. Maybe the synaptics is the problem -
perhaps I need libinput and indeed in the version you mention. So that
is yet another thing to yest (isn't this someone's actual job?). Also, I
*like* synaptics; I do not want to use libinput.

> Have you tested if a second suspend/resume cycle revives the touchpad?

I think so.

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

[Kernel-packages] [Bug 1785198] Re: mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on Trusty

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Importance: High => Undecided

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

Title:
  mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on
  Trusty

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

Bug description:
  This test failed due to:
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 /
  pwrite03_64 / setxattr01 are failing with the same issue.

  The mkfs.vfat command only works once for the first test.

  So if you run the same test case (e.g. msync04) on a recently rebooted
  system, it will pass for the first run.

  <<>>
  tag=fallocate05 stime=1533288629
  cmdline="fallocate05"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  incrementing stop
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1079: INFO: Testing on ext2
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext3
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext4
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on xfs
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on vfat
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  Summary:
  passed   8
  failed   0
  skipped  2
  warnings 0
  <<>>
  initiation_status="ok"
  duration=8 termination_type=exited termination_id=2 corefile=no
  cutime=6 cstime=105
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20180515

   

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Radu Andries]

Same issue here.

Adding this to options + cold boot seems to have fixed it.

% cat /etc/modprobe.d/btusb.conf
options btusb enable_autosuspend=0
~ % uname -r
4.18.19-041819-generic

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice:
   RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93
   #RESUME=/dev/dm-2
   #RESUME=/dev/mapper/regan-swap
  InstallationDate: Installed on 2016-12-22 (619 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.

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

[Ubuntu Kernel Bot]

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

apport-collect 1804804

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

Title:
  Screen rotation does not rotate all input devices and needs custom
  user commands (iio-sensor-proxy or libinput should probably handle
  this?)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10
  GNOME Shell 3.30.1
  Cinnamon 3.8.8

  Hardware: ASUS Transformer Mini.

  Also confirmed problematic for Yoga Series tablet/laptop hybrids.
  (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)

  Screen rotation works fine, but tablet coords including touch screen
  and pen coords do not rotate with it.

  Gnome gets touch screen rotation correct, but not pen coords
  Cinnamon gets touch screen rotation and peen coords wrong

  User can correct using convoluted xinput commands like:
  xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate 
Transformation Matrix" 0 1 0 -1 0 1 0 0 1

  I spoke with Mint devs who said I should file it against iio-sensor-
  proxy or libinput, which I assume is a better solution that asking
  various wm developers to fix it individually.

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

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

[Kernel-packages] [Bug 1785198] Re: mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on Trusty

[Po-Hsu Lin]

This is greatly affecting the test process, as it's causing many false
alarms, and the failed test cases number are growing.

** Summary changed:

- mkfs.vfat is causing failure on  fallocate05, fsetxattr01, fgetxattr01, 
fsync01, msync04, preadv03, preadv03, pwritev03, pwritev03_64, setxattr01 tests 
in ubuntu_ltp_syscall on Trusty
+ mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on Trusty

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

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => High

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

Title:
  mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on
  Trusty

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

Bug description:
  This test failed due to:
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 /
  pwrite03_64 / setxattr01 are failing with the same issue.

  The mkfs.vfat command only works once for the first test.

  So if you run the same test case (e.g. msync04) on a recently rebooted
  system, it will pass for the first run.

  <<>>
  tag=fallocate05 stime=1533288629
  cmdline="fallocate05"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  incrementing stop
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1079: INFO: Testing on ext2
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext3
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext4
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on xfs
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079:

[Kernel-packages] [Bug 1804804] [NEW] Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)

[Christopher M. Rogers]

Public bug reported:

Ubuntu 18.10
GNOME Shell 3.30.1
Cinnamon 3.8.8

Hardware: ASUS Transformer Mini.

Also confirmed problematic for Yoga Series tablet/laptop hybrids.
(https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)

Screen rotation works fine, but tablet coords including touch screen and
pen coords do not rotate with it.

Gnome gets touch screen rotation correct, but not pen coords
Cinnamon gets touch screen rotation and peen coords wrong

User can correct using convoluted xinput commands like:
xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate Transformation 
Matrix" 0 1 0 -1 0 1 0 0 1

I spoke with Mint devs who said I should file it against iio-sensor-
proxy or libinput, which I assume is a better solution that asking
various wm developers to fix it individually.

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


** Tags: iio-sensor-proxy libinput

** Tags added: libinput

** Summary changed:

- Screen rotation does not rotate all input devices and needs custom user 
commands
+ Screen rotation does not rotate all input devices and needs custom user 
commands (iio-sensor-proxy or libinput should probably handle this)

** Summary changed:

- Screen rotation does not rotate all input devices and needs custom user 
commands (iio-sensor-proxy or libinput should probably handle this)
+ Screen rotation does not rotate all input devices and needs custom user 
commands (iio-sensor-proxy or libinput should probably handle this?)

** Description changed:

+ Ubuntu 18.10
+ GNOME Shell 3.30.1
+ Cinnamon 3.8.8
+ 
+ Hardware: ASUS Transformer Mini.
+ 
+ Also confirmed problematic for Yoga Series tablet/laptop hybrids.
+ (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)
+ 
  Screen rotation works fine, but tablet coords including touch screen and
  pen coords do not rotate with it.
  
  Gnome gets touch screen rotation correct, but not pen coords
  Cinnamon gets touch screen rotation and peen coords wrong
  
  User can correct using convoluted xinput commands like:
  xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate 
Transformation Matrix" 0 1 0 -1 0 1 0 0 1
  
  I spoke with Mint devs who said I should file it against iio-sensor-
  proxy or libinput, which I assume is a better solution that asking
  various wm developers to fix it individually.

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

Title:
  Screen rotation does not rotate all input devices and needs custom
  user commands (iio-sensor-proxy or libinput should probably handle
  this?)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10
  GNOME Shell 3.30.1
  Cinnamon 3.8.8

  Hardware: ASUS Transformer Mini.

  Also confirmed problematic for Yoga Series tablet/laptop hybrids.
  (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)

  Screen rotation works fine, but tablet coords including touch screen
  and pen coords do not rotate with it.

  Gnome gets touch screen rotation correct, but not pen coords
  Cinnamon gets touch screen rotation and peen coords wrong

  User can correct using convoluted xinput commands like:
  xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate 
Transformation Matrix" 0 1 0 -1 0 1 0 0 1

  I spoke with Mint devs who said I should file it against iio-sensor-
  proxy or libinput, which I assume is a better solution that asking
  various wm developers to fix it individually.

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

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

[Kernel-packages] [Bug 872711] Re: Kernel does not report some USB printers correctly, making them not being detected by CUPS

[Colin Watson]

** Attachment removed: "printrtr.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/872711/+attachment/5212583/+files/printrtr.jpg

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

Title:
  Kernel does not report some USB printers correctly, making them not
  being detected by CUPS

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Oneiric:
  Fix Released
Status in linux source package in Precise:
  Fix Released

Bug description:
  See the following CUPS upstream bug report:

  http://www.cups.org/str.php?L3884

  Users complain that their USB printers do not get detected by CUPS and
  so they cannot set them up for printing. In the last comment it is
  told that the kernel is the culprit and a link to a patch proposal on
  the Kernel mailing list is given:

  http://lkml.org/lkml/2011/9/25/57

  The patch attached there is supposed to solve the problem.

  I have also a printer (HP Color LaserJet CM3530 MFP) which is only
  detected by the HPLIP CUPS backend (this backend uses another
  detection method but is only avaiolable for HP printers) and not by
  CUPS' own backend, so I can reproduce the bug.

  I did not test the kernel patch.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  till   2561 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc02 irq 48'
 Mixer name : 'Conexant CX20561 (Hermosa)'
 Components : 'HDA:14f15051,17aa211c,0010'
 Controls  : 17
 Simple ctrls  : 9
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7VHT12WW-1.01'
 Mixer name : 'ThinkPad EC 7VHT12WW-1.01'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9185f036-2e72-40e6-bf31-d9a8926a7883
  MachineType: LENOVO 7417CTO
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 product info: "MoGo Mouse BT", " ", "", ""
  PccardctlStatus:
   Socket 0:
 5.0V 16-bit PC Card
 Subdevice 0 (function 0) [unbound]
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  StagingDrivers: mei
  Tags:  oneiric running-unity staging
  Uname: Linux 3.0.0-12-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-09-30 (11 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 10/13/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET79WW (3.09 )
  dmi.board.name: 7417CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET79WW(3.09):bd10/13/2009:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7417CTO
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 818544] Re: Brother MFC-240C FAX/Printer error

[Colin Watson]

** Attachment removed: "printrtr.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818544/+attachment/5211037/+files/printrtr.jpg

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

Title:
  Brother MFC-240C FAX/Printer error

Status in linux package in Ubuntu:
  Expired

Bug description:
  Before the extensive listing.  I had the printer working fine through
  manually installing the printer drivers from the Brother software site
  since 9.10, and also for a HP printer.  A couple weeks back, the
  universal printer drivers were changed on my Computer via a popup
  updater (damned thing).  I tried removing everything, and re-
  installing the origional printers.  One problem is most of the online
  help is for the older 10.10, and is always using menues that have been
  removed.  I also busted out my linux manual and used the lpadmin, and
  manually configuring cups.  The cups file looks fine, but constantly
  changes permissions every ten minutes to only allow root to access it.
  In addition I get the following error:

  lpinfo: cups-driverd failed to execute.
  cupsd: Child exited on signal 15!

  The main error printed starts like this:

  Cannot execute command due to filter
  stopping job because scheduler cannot execute filter

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

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

[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters

[ Christian Ehrhardt ]

** Changed in: libvirt (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: libvirt (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: qemu (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: qemu (Ubuntu Cosmic)
   Status: New => Triaged

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  In Progress
Status in libvirt package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress
Status in libvirt source package in Bionic:
  Triaged
Status in linux source package in Bionic:
  Fix Committed
Status in qemu source package in Bionic:
  Triaged
Status in libvirt source package in Cosmic:
  Triaged
Status in linux source package in Cosmic:
  Fix Committed
Status in qemu source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0

[Kernel-packages] [Bug 1802283] Re: system freezes

[jnns]

Another day, another freeze. Even with the new firmware installed. It
ofen occurs during video chats. I wonder if CPU usage has something to
do with it.


** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+attachment/5215568/+files/kern.log

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

Title:
  system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Thorsten]

Hi, I also have the :00:1f.4 and the nfc model (20KG-S03900) and I
don’t have this issue. Even my trackpoint now survives resumes/suspends
since using 4.19.1 and upgrading all firmware (using windows)
(touchpad/trackpoint/bios/thunderbolt).

I can just repeat the steps, which where necessary for me on ubuntu
18.04.1:

1. Removing the blacklisting of i2c_i801 in /etc/modprobe but this is now 
default in ubuntu 18.04 (see: https://bugs.launchpad.net/hwe-next/+bug/1786574 )
2. Installing a newer kernel from mainline ppa: currently using 4.19.2
3. Using libinuput 1.12.1-1 and xserver-xorg-input-libinput with:
sudo dpkg -i libinput10_1.12.1-1_amd64.deb  libinput-bin_1.12.1-1_amd64.deb  
xserver-xorg-input-libinput_0.28.1-1_amd64.deb  the files are available here: 
https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput and 
https://launchpad.net/ubuntu/+source/libinput 
(4.) I also use the padoka stable mesa ppa.

Maybe it would help if we identify the differences between our devices.
Have you tested if a second suspend/resume cycle revives the touchpad?

-- 
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 00

[Kernel-packages] [Bug 1802578] Re: [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22

[Alexander Karlstad]

I can confirm that this is happening less frequent after applying
workaround from bug 1552040.

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

Title:
  [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed
  with -22

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This error appears in my journal quite often after resuming laptop
  from suspend and when un-docking the machine in the meantime.

  When docked, I usually only enable two external displays. Un-docked I
  only have the built-in display on the laptop. This was working
  flawlessly in 18.04 but is extremely buggy now after having upgraded
  to 18.10 for some reason.

  When this happens, my screen(s) remain pitch black. Switching to TTYs
  and back does not help. CTRL+ALT+F1 gives me the GDM login, but when
  entering password it seems it switches to TTY2 (or whatever is at
  CTRL+ALT+F2), and the screen(s) remain black.

  Logging in in a TTY and trying to "DISPLAY=:0.0 gnome-shell --replace"
  does not help.

  +P does not work (is this shortcut combination removed?).

  At last when I ran "xrandr --auto" the session I had crashed and I had
  to re-login, but at least this time I got my desktop.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexander  23057 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  9 20:34:53 2018
  HibernationDevice: RESUME=/swapfile
  InstallationDate: Installed on 2018-05-02 (190 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20HN0013MX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash net.ifnames=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-11-01 (7 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET55W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0013MX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET55W(1.33):bd09/14/2018:svnLENOVO:pn20HN0013MX:pvrThinkPadX270:rvnLENOVO:rn20HN0013MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0013MX
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters

[ Christian Ehrhardt ]

Integrated the upcoming qemu CVE fixes as well as another SRU fix going
on currently into the builds of our PPA. Also I forked a branch for
18.10 for the same changes.

With that I started the cross arch regression check (still ongoing - and
will for a while)

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  In Progress
Status in libvirt package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed s

[Kernel-packages] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel

[Po-Hsu Lin]

** Tags added: cosmic

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

Title:
  ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-kvm source package in Xenial:
  New

Bug description:
  The "enable disable fan test" will fail with Xenial KVM kernel

  Error message:
RTNETLINK answers: Operation not supported
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 
0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanatic: unable to bring fan up, unable to configure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
  ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
  Uname: Linux 4.4.0-1021-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 10:22:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

[AaronMa]

** Description changed:

- After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on
- Lenovo 11e 2nd gen machines.
+ SRU:
+ 
+ 
+ [Impact]
+ ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
+ PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
+ runtime suspend mode in old touchpad fw.
+ Then touchpad will not work.
+ LEN2040 on 11e 3rd can reproduce this issue by passing
+ psmouse.synaptics_intertouch=1
+ 
+ These 2 pnp device should be the same one Synaptics s3203_ver5.
+ 
+ [Fix]
+ i2c-i801 should auto suspend when not used, no need runtime pm.
+ 
+ [Test Case]
+ Tested on Thinkpad 11e 3rd.
+ Touchpad works fine.
+ 
+ [Regression Potential]
+ Low, upstream fix cherry-picked.
+ 
+ 4.18 kernel patch, no need for cosmic.
+ 
+ 
+ Original bug report:
+ =
+ After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.
  
  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.
  
  We are currently working around the issue by deploying our own blacklist
  files.
  
  Here is a link to the SRU justification: https://bugs.launchpad.net/hwe-
  next/+bug/1786574

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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

[Kernel-packages] [Bug 1752437] Re: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #201121
   https://bugzilla.kernel.org/show_bug.cgi?id=201121

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

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

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1752437]

[luya]

(In reply to Maxime from comment #87)
> I applied the latest patch, it works but it makes my touchscreen show up as
> having a battery that's at 0%. The previous patch had the same behaviour on
> my system.

Similar bug on https://bugzilla.kernel.org/show_bug.cgi?id=201121
It looks like the issue affecting Elan touchscreen and stylus models.

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

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

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1776563]

[eutychios23]

I cannot reboot,shutdown,suspend in fedora with kernel 4.19.2, kernel
4.18.6 works fine,no errors in dmesg, how is kernel 4.19.x working for
you in various distros?

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1790880] Re: apt-get source linux-image-$(uname -r) does not work on 18.04.1 LTS

[Jean Franco Amoni Rodríguez]

Same trying follow https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel on
Ubuntu 18.04.1

$ apt-get source linux-image-$(uname -r)
Reading package lists... Done
Picking 'linux-signed' as source package instead of 
'linux-image-4.15.0-39-generic'
E: Unable to find a source package for linux-signed

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

Title:
  apt-get source linux-image-$(uname -r) does not work on 18.04.1 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot get the source code and therefore cannot build a driver for
  Ubuntu 18.04.1 LTS

  See link

  https://ubuntuforums.org/showthread.php?t=2397649

  Other people have seen the same problem.

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

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