[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

2020-06-10 Thread Anthony Wong
** Changed in: linux (Ubuntu Focal)
   Status: New => Invalid

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in linux package in Ubuntu:
  Invalid
Status in wpa package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in wpa source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Invalid
Status in wpa source package in Groovy:
  Confirmed

Bug description:
  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

2020-06-10 Thread Mats Blakstad
I'm using Asus UX305CA, have the same problem.

The workaround I use for now is to reinstall the system, then before
updating I make sure intel-microcode is put on hold:

sudo apt-mark hold intel-microcode

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymouth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  - reinstall cryptsetup & update-grub (as suggested in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 )

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

  EDIT:

  Hypothesis:
  Only affects ASUS with i7-8565U Whiskey Lake Intel CPU

  Upstream Bug Report:
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

  WORKAROUND 1: disable intel microcode updates during boot
  From this bug: 
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
  1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
  2/ update-grub

  WORKAROUND 2: downgrade (and hold) intel-microcode to older version from 
bionic/main
  apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1

  WORKAROUND 3: upgrade BIOS
  Asus has released updated BIOSes, which probably include the newest 
microcode. After upgrading workarounds 1,2 are not needed. 
  Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be 
(easily) reverted. 

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2339 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Tags: third-party-packages bionic wayland-session
  Uname: Linux 5.0.0-15-generic x86_64
  UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny 
balíky třetích stran a zkuste to znovu.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions

-- 

[Kernel-packages] [Bug 1881435] Re: System freeze

2020-06-10 Thread Nitro Kash
I was not getting system freeze for a while. But, in the last two days,
it froze three times. All three times I was watching a video or in a
Google Meet meeting. I am attaching the output to "journalctl -b-1" from
the last freeze.

** Attachment added: "prevboot3.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881435/+attachment/5382309/+files/prevboot3.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/1881435

Title:
  System freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes randomly. Keyboard and mouse do not work at that time. I am 
not able to ssh to the computer or access tty. I am able to do only a hard 
reset. I tried some troubleshooting myself, but with my novice expertise with 
ubuntu. The freeze is more or less random. But it is possibly more frequent 
when running a video, like a youtube video in a browser. Freeze is more 
frequenty when going full screen with a video, a VM machine or a remote desktop 
through vnc4server.
  1. Tried removing some software like chrome, dropbox, virtualbox, etc. That 
did not help.
  2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 
kernel. That did not help either.
  3. Tried other distros like Mint and Fedora. Still had problem.
  4. Tried running with NVidia driver and xserver-xorg. The problem occured 
with both.
  5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured 
in both. 
  6. Tried all the suggestions in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were 
applicable. None of the suggestions helped.
  7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and 
experienced no crash/freeze with youtube running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 12:36:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651]
  InstallationDate: Installed on 2020-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  

[Kernel-packages] [Bug 1870320] Re: [UBUNTU 18.04] zpcictl --reset - contribution for kernel

2020-06-10 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 18.04] zpcictl --reset - contribution for kernel

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * With zpci_disable() working, 'lockdep' detected a potential deadlock
  (in the s390x zPCI subsystem).

  * The deadlock is between recovering a PCI function via the
  /sys/bus/pci/devices//recover attribute vs powering it off via
  /sys/bus/pci/slots//power.

  [Fix]

  * Backport 1: https://launchpadlibrarian.net/479554961/0001-s390-pci-
  Recover-handle-in-clp_set_pci_fn.patch

  * Backport 2: https://launchpadlibrarian.net/478714295/0001-s390-pci-
  Fix-possible-deadlock-in-recover_store.patch

  [Test Case]

  * It's best to (re-)test using the kernel's locking validator, also
  known as 'lockdep'.

  * Since this potential deadlock was identified by lockdep.

  [Regression Potential]

  * The regression potential can be considered as moderate, since:

  * It is purely s390x specific code (arch/s390/include/asm/pci.h and
  arch/s390/pci/{pci.c,pci_clp.c,pci_sysfs.c}).

  * It only affects the zPCI, the s390x specific PCI code layer.

  * PCI cards available for s390x are optional cards (RoCE and zEDC) and
  not very wide-spread.

  * The states between such a deadlock can happen (recover and power
  off) are non standard and usually undesired states.

  * The patches are upstream accepted since 5.6 and already landed in
  eoan and focal.

  [Other Info]

  * Patches 17cdec960cf7 "s390/pci: Recover handle in clp_set_pci_fn()"
  and 576c75e36c68 "s390/pci: Fix possible deadlock in recover_store()"
  are upstream accepted since kernel 5.6, but they don't apply cleanly
  on bionic master-next, hence backports are needed:

  * 0001-s390-pci-Recover-handle-in-clp_set_pci_fn.patch is a backport
  of 17cdec960cf776b20b1fb08c61babe591d51 17cdec960cf7 "s390/pci:
  Recover handle in clp_set_pci_fn()"

  * 0001-s390-pci-Fix-possible-deadlock-in-recover_store.patch is a
  backport of 576c75e36c689bec6a940e807bae27291ab0c0de 576c75e36c68
  "s390/pci: Fix possible deadlock in recover_store()"

  * Both patches/commits already landed in focal (with LP 1863768) and in eoan 
(with LP 1868324).
  __

  This Bug tracks the necessary backport for the Linux Kernel
  to enable proper reset/recovery of PCI Functions in the error state.
  There is a related fix to s390-tools but the relevant zpcictl command
  is not part of Ubuntu 18.04

  Upstream this includes the following commits:

  In the Kernel:

  17cdec960cf776b20b1fb08c61babe591d51 s390/pci: Recover handle in 
clp_set_pci_fn()
  Backport patch attached.

  576c75e36c689bec6a940e807bae27291ab0c0de s390/pci: Fix possible deadlock in 
recover_store()
  applies cleanly but for the second a small backport change is necessary.

  These fixes are already in 20.04 but need also be applied to 18.04.

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

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


[Kernel-packages] [Bug 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

2020-06-10 Thread Timo Aaltonen
this is supposedly fixed by a stable tree commit in 5.6, marking
verified

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

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  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:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background

2020-06-10 Thread Daniel van Vugt
Thanks for the suggestion. Unfortunatley vt.handoff=1 did not improve
the situation.


** Tags added: groovy

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

Title:
  Display flickers (monitor loses signal briefly) during "flickerfree"
  boot, while showing the BIOS logo on a black background

Status in Plymouth:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  I am trying flickerfree boot in 19.10 [1], but find it actually
  flickers part way through:

1. BIOS logo on a black background.
2. Display mode resets, no image on a black background briefly.
3. BIOS logo on a black background.

  The flicker occurs seemingly during kernel startup since my
  peripherals are lit up before the problem occurs.

  Suspecting this might be related to FB handover:

    [2.751028] fb0: switching to inteldrmfb from EFI VGA

  I tried disabling that with a big hammer:

    i915.modeset=0

  so it stays in efifb, and that works -- no more flickering, providing
  I don't let i915 take over the framebuffer.

  [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 17 16:34:36 2019
  InstallationDate: Installed on 2019-05-02 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  MachineType: LENOVO 10M7CTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3

2020-06-10 Thread Timo Aaltonen
this is supposed to be fixed in focal by a stable tree commit

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

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Wyse 5070 Thin Client
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Wyse Thin Client 5000 Series
  dmi.product.name: Wyse 5070 Thin Client
  dmi.product.sku: 080C
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

2020-06-10 Thread Thoo
Ahoy,

on 18.04 LTS bionic I have been offered kernel linux-
image-4.15.0-106-generic when using "apt-get dist-upgrade".

Since for me the last working kernel 4.15.0-96-generic is almost to be
rolled out of my grub config with this new 4.15.0-106 kernel, I'd like
to know if this bug is fixed in the 106 kernel.

Alternatively:

How do I pin the working 4.15.0-96-generic kernel to my grub config, so
that further kernel updates via "apt-get dist-upgrade" don't roll my
working 4.15.0-96-generic kernel out of my grub config automagically?

And secondly: Is there a similar "proposed" method as mentioned in
comment #38 for bionic that I can test a proposed kernel with a fix on
bionic "safely" with an *easy* option to roll back?

(Installing the provided test-kernel from comment #19, and trying to
revert back to a standard kernel did not work out that well for me, see
comments #27, #28 and #31.)

Thanks

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  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:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2020-06-10 03:21 EDT---
IBM Bugzilla closed, Fix Released with requested Distro

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

Title:
  [UBUNTU 18.04] zpcictl --reset - contribution for kernel

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * With zpci_disable() working, 'lockdep' detected a potential deadlock
  (in the s390x zPCI subsystem).

  * The deadlock is between recovering a PCI function via the
  /sys/bus/pci/devices//recover attribute vs powering it off via
  /sys/bus/pci/slots//power.

  [Fix]

  * Backport 1: https://launchpadlibrarian.net/479554961/0001-s390-pci-
  Recover-handle-in-clp_set_pci_fn.patch

  * Backport 2: https://launchpadlibrarian.net/478714295/0001-s390-pci-
  Fix-possible-deadlock-in-recover_store.patch

  [Test Case]

  * It's best to (re-)test using the kernel's locking validator, also
  known as 'lockdep'.

  * Since this potential deadlock was identified by lockdep.

  [Regression Potential]

  * The regression potential can be considered as moderate, since:

  * It is purely s390x specific code (arch/s390/include/asm/pci.h and
  arch/s390/pci/{pci.c,pci_clp.c,pci_sysfs.c}).

  * It only affects the zPCI, the s390x specific PCI code layer.

  * PCI cards available for s390x are optional cards (RoCE and zEDC) and
  not very wide-spread.

  * The states between such a deadlock can happen (recover and power
  off) are non standard and usually undesired states.

  * The patches are upstream accepted since 5.6 and already landed in
  eoan and focal.

  [Other Info]

  * Patches 17cdec960cf7 "s390/pci: Recover handle in clp_set_pci_fn()"
  and 576c75e36c68 "s390/pci: Fix possible deadlock in recover_store()"
  are upstream accepted since kernel 5.6, but they don't apply cleanly
  on bionic master-next, hence backports are needed:

  * 0001-s390-pci-Recover-handle-in-clp_set_pci_fn.patch is a backport
  of 17cdec960cf776b20b1fb08c61babe591d51 17cdec960cf7 "s390/pci:
  Recover handle in clp_set_pci_fn()"

  * 0001-s390-pci-Fix-possible-deadlock-in-recover_store.patch is a
  backport of 576c75e36c689bec6a940e807bae27291ab0c0de 576c75e36c68
  "s390/pci: Fix possible deadlock in recover_store()"

  * Both patches/commits already landed in focal (with LP 1863768) and in eoan 
(with LP 1868324).
  __

  This Bug tracks the necessary backport for the Linux Kernel
  to enable proper reset/recovery of PCI Functions in the error state.
  There is a related fix to s390-tools but the relevant zpcictl command
  is not part of Ubuntu 18.04

  Upstream this includes the following commits:

  In the Kernel:

  17cdec960cf776b20b1fb08c61babe591d51 s390/pci: Recover handle in 
clp_set_pci_fn()
  Backport patch attached.

  576c75e36c689bec6a940e807bae27291ab0c0de s390/pci: Fix possible deadlock in 
recover_store()
  applies cleanly but for the second a small backport change is necessary.

  These fixes are already in 20.04 but need also be applied to 18.04.

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

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


[Kernel-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format

2020-06-10 Thread Alex Tu
$ v4l2-ctl -D -d /dev/video0 --list-formats-ext
Driver Info:
Driver name  : uvcvideo
Card type: Integrated_Webcam_HD: Integrate
Bus info : usb-:00:14.0-6
Driver version   : 5.6.14
Capabilities : 0x84a1
Video Capture
Metadata Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps  : 0x0421
Video Capture
Streaming
Extended Pix Format
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture

[0]: 'MJPG' (Motion-JPEG, compressed)
Size: Discrete 1280x720
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 960x540
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 848x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 640x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 640x360
Interval: Discrete 0.033s (30.000 fps)
[1]: 'YUYV' (YUYV 4:2:2)
Size: Discrete 640x480
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 640x360
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 424x240
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 320x240
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 320x180
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 160x120
Interval: Discrete 0.033s (30.000 fps)

** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #28
   https://gitlab.gnome.org/GNOME/cheese/-/issues/28

** Also affects: cheese via
   https://gitlab.gnome.org/GNOME/cheese/-/issues/28
   Importance: Unknown
   Status: Unknown

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => High

** Tags added: oem-priority originate-from-1881688 somerville

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

Title:
  cheese not recognize resolution in MJPG format

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  reproduce step:
   - open cheese
   - open preferences -> resolution
   - only resolution from YUYV format in options

  the patches there works well and waiting for merge:
  https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1build1
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:23:02 2020
  InstallationDate: Installed on 2020-04-12 (58 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  RelatedPackageVersions:
   cheese3.34.0-1build1
   cheese-common 3.34.0-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1882039] Re: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs

2020-06-10 Thread Stefan Bader
For the current development this will be automatically fixed once the
kernel moves to 5.7 (the fix was in 5.5). I leave it to the devel team
whether they want to keep the task open until then.

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

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

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

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

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

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

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

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

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

Title:
  The thread level parallelism would be a bottleneck when searching for
  the shared pmd by using hugetlbfs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Impact]

  There is performance overhead observed when many threads
  are using hugetlbfs in the database environment.

  [Fix]

  bdfbd98bc018 hugetlbfs: take read_lock on i_mmap for PMD sharing

  The patch improves the locking by using the read lock instead of the
  write lock. And it allows multiple threads searching the suitable shared
  VMA. As there is no modification inside the searching process. The 
  improvement increases the parallelism and decreases the waiting time of
  the other threads.

  [Test]

  The customer stand-up a database with seed data. Then they have a
  loading "driver" which makes a bunch of connections that look like user
  workflows from the database perspective. Finally, the measuring response
  times improvement can be observed for these "users" as well as various
  other metrics at the database level.

  [Regression Potential]

  The modification is only in replacing the write lock to a read one. And 
  there is no modification inside the loop. The regression probability is
  low.

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

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


[Kernel-packages] [Bug 1880580] Re: zpool import PANIC at zio.c:266

2020-06-10 Thread Colin Ian King
Can you try to temporarily disable the spa verification to see if this
allows the import to at least complete to see if this helps.

echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_metadata
echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_data

do the import, and then re-enable:

echo 1 | sudo tee /sys/module/zfs/parameters/spa_load_verify_metadata
echo 1 | sudo tee /sys/module/zfs/parameters/spa_load_verify_data


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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  zpool import PANIC at zio.c:266

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  3)
  After a reboot, ZFS pool never stopped trying to import the pool. It was 
blocking the boot-sequence and I had to rename the /etc/zfs/zpool.cache to 
another name, in order to boot the system.
  There was an upgrade made before reboot, but that was not anything with zfs.

  
  The problem is that zpool datastore is not possible to import in normal way. 
Only in readonly=on is I able to import it.
  Also the Scub seems to be active on the readonly, but it will never stops 
since it not possible to write to the pool.
  I cannot stop scrub either since I can only import it at readonly.

  
  If I import it at readonly it works and I can access the files. But if import 
normally a panic occur, and the process hangs.

  4)
  Expected to be able to import the zpool as normal.

  
  1)
  #lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  2)
  #apt-cache policy zfsutils-linux
  zfsutils-linux:
Installerad: 0.7.5-1ubuntu16.9
Kandidat:0.7.5-1ubuntu16.9


  # dpkg -l | grep -i "zfs"
  rc  libzfs10.6.2-1~precise
 amd64Native ZFS filesystem library for Linux
  rc  libzfs20.6.5.4-1~precise  
 amd64Native OpenZFS filesystem library for Linux
  ii  libzfs2linux   0.7.5-1ubuntu16.9  
 amd64OpenZFS filesystem library for Linux
  rc  libzpool1  0.6.2-1~precise
 amd64Native ZFS pool library for Linux
  rc  libzpool2  0.6.5.4-1~precise  
 amd64Native OpenZFS pool library for Linux
  ii  libzpool2linux 0.7.5-1ubuntu16.9  
 amd64OpenZFS pool library for Linux
  rc  ubuntu-zfs 8~precise  
 amd64Native ZFS filesystem metapackage for Ubuntu.
  rc  zfs-dkms   0.7.5-1ubuntu16.9  
 all  OpenZFS filesystem kernel modules for Linux
  ii  zfs-doc0.7.5-1ubuntu16.9  
 all  Native OpenZFS filesystem documentation and examples.
  ii  zfs-initramfs  0.7.5-1ubuntu16.9  
 all  OpenZFS root filesystem capabilities for Linux - 
initramfs
  ii  zfs-zed0.7.5-1ubuntu16.9  
 amd64OpenZFS Event Daemon
  rc  zfsutils   0.6.5.4-1~precise  
 amd64Native OpenZFS management utilities for Linux
  ii  zfsutils-linux 0.7.5-1ubuntu16.9  
 amd64command-line tools to manage OpenZFS filesystems

  
  #zpool status
  no pools available

  # zpool import
 pool: datastore
   id: 3190464655986727485
state: ONLINE
   status: Some supported features are not enabled on the pool.
   action: The pool can be imported using its name or numeric identifier, though
  some features will not be available without an explicit 'zpool 
upgrade'.
   config:

  datastore   ONLINE
raidz2-0  ONLINE
  sdb ONLINE
  sdc ONLINE
  sdd ONLINE
  sde ONLINE
  sdf ONLINE
  sdg ONLINE


  # zpool import -o readonly=on datastore
  # zpool status
pool: datastore
   state: ONLINE
  status: Some supported features are not enabled on the pool. The pool can
  still be used, but some features are unavailable.
  action: Enable all features using 'zpool upgrade'. Once this is done,
  the pool may no longer be accessible by software that does not support
  the features. See zpool-features(5) for details.
scan: scrub in 

[Kernel-packages] [Bug 1877928] Re: focal/linux-raspi: Upstream raspberrypi patchset 2020-05-11

2020-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi - 5.4.0-1012.12

---
linux-raspi (5.4.0-1012.12) focal; urgency=medium

  * focal/linux-raspi: 5.4.0-1012.12 -proposed tracker (LP: #1878791)

  * Focal update: v5.4.36 upstream stable release (LP: #1876361)
- [Config] raspi: updateconfigs for ARM64_ERRATUM_1542419

  * Raspberry Pi 4B: USB OTG is not working (LP: #1861070)
- [Config] raspi: Set USB_DWC2_DUAL_ROLE=y

  * Missing v3d driver disables 3D support on RPi4 (LP: #1876862)
- [Config] raspi: Set DRM_V3D=m

  * focal/linux-raspi: Upstream raspberrypi patchset 2020-05-11 (LP: #1877928)
- SAUCE: media: bcm2835-unicam: Resync to upstream raspberrypi
- media: bcm2835-unicam: Add support for mulitple device nodes.
- media: bcm2835-unicam: Add embedded data node.
- media: bcm2835-unicam: Use dummy buffer if none have been queued
- media: bcm2835-unicam: Disable event-related ioctls on metadata node
- media: bcm2835-unicam: Add support for the FRAME_SYNC event
- media: imx219: Advertise embedded data node on media pad 1
- dts: bcm2711: EMMC2 can address the whole first GB
- driver: char: rpivid: Remove legacy name support
- driver: char: rpivid: Don't map more than wanted
- defconfig: Enable I2C_MUX_PINCTRL in all Pi configs
- dt: Implement an I2C pinctrl mux for BSC0.
- dtoverlays: Update CSI overlays to use i2c_csi_dsi
- dt: Update all mainline bcm283x dt files for i2c0 pinctrl mux
- ARM: dts: Create bcm2708-rpi-b-rev1.dts
- dts: bcm2711: set #size-cells = <2>
- dts: bcm2711: add "High Peripheral" mode overlay
- Revert "spi: spidev: Fix CS polarity if GPIO descriptors are used"
- spi: use_gpio_descriptor fixup moved to spi_setup
- overlays: rpivid-v4l2 also needs size-cells = 2
- media: bcm2835-unicam: Re-fetch mbus code from subdev on a g_fmt call
- uapi: bcm2835-isp: Add bcm2835-isp uapi header file
- media: uapi: v4l2-core: Add ISP statistics output V4L2 fourcc type
- media: uapi: v4l-ctrls: Add CID base for the bcm2835-isp driver
- staging: mmal-vchiq: Fix formatting errors in mmal_parameters.h
- staging: vc04_services: ISP: Add a more complex ISP processing component
- staging: vchiq: Load bcm2835_isp driver from vchiq
- configs: Add VIDEO_ISP_BCM2835 to all Pi defconfigs
- vc4_hvs: Mark core clock as optional
- vc4_hdmi: BCM2835 requires a fixed hsm clock for CEC to work
- configs: Enable CONFIG_DRM_VC4_HDMI_CEC
- media: i2c: imx219: Implement get_selection
- media: i2c: ov5647: Add support for g_selection to reflect 
cropping/binning
- media: i2c: ov5467: Fixup error path to release mutex
- media: i2c: ov5647: Support V4L2_CID_PIXEL_RATE
- media: i2c: ov5647: Set V4L2_SUBDEV_FL_HAS_EVENTS flag
- media: i2c: ov5647: Add support for V4L2_CID_VBLANK
- media: i2c: ov5647: Neither analogue gain nor exposure need 
EXECUTE_ON_WRITE
- media: i2c: ov5647: Use member names in mode tables
- media: i2c: ov5647: Advertise the correct exposure range
- media: i2c: imx219: Declare that the driver can create events
- media: bcm2835-unicam: Add support for VIDIOC_[S|G]_SELECTION
- media: bcm2835-unicam: Do not stop streaming in unicam_release
- media: bcm2835-unicam: Fix reference counting in unicam_open
- staging: vc04_services: ISP: Add enum_framesizes ioctl
- SQUASH: spi: Demote SPI_CS_HIGH warning to KERN_DEBUG
- ARM: dts: bcm2711: Allow 40-bit DMA for SPI
- overlays: Make the i2c-gpio overlay safe again
- staging: vc04_services: isp: Remove duplicated initialisation
- staging: vc04_services: isp: Make all references to bcm2835_isp_fmt const
- overlays: gpio-keys: Avoid open-drain warnings
- configs: Add missing PPS configs
- configs: Add missing TOUCHSCREEN_RASPBERRYPI_FW=m
- vc4_hdmi_phy: Fix typo in phy_get_cp_current
- overlays: Make use of intra-overlay fragments
- media: i2c: tc358743: Fix fallthrough warning
- media: bcm2835: unicam: Fix uninitialized warning
- video: bcm2708_fb: Disable FB if no displays found
- overlays: sc16is752-spi1: Add xtal parameter
- vc4_hdmi: Fix register offset when sending longer CEC messages
- vc4_hdmi: Fix up CEC registers
- vc4_hdmi_regs: Add Intr2 register block
- vc4_hdmi_regs: Make interrupt mask variant specific
- vc4_hdmi: Make irq shared
- vc4_hdmi: Adjust CEC ref clock based on its input clock
- vc4_hdmi: Remove cec_available flag as always supported
- config: Enable CONFIG_DRM_VC4_HDMI_CEC
- [Config] raspi: updateconfigs after update to rpi-5.4.y

  [ Ubuntu: 5.4.0-34.38 ]

  * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118)
  * debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
  * Focal update: v5.4.41 upstream stable release (LP: #1878649)
- USB: 

[Kernel-packages] [Bug 1876862] Re: Missing v3d driver disables 3D support on RPi4

2020-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi - 5.4.0-1012.12

---
linux-raspi (5.4.0-1012.12) focal; urgency=medium

  * focal/linux-raspi: 5.4.0-1012.12 -proposed tracker (LP: #1878791)

  * Focal update: v5.4.36 upstream stable release (LP: #1876361)
- [Config] raspi: updateconfigs for ARM64_ERRATUM_1542419

  * Raspberry Pi 4B: USB OTG is not working (LP: #1861070)
- [Config] raspi: Set USB_DWC2_DUAL_ROLE=y

  * Missing v3d driver disables 3D support on RPi4 (LP: #1876862)
- [Config] raspi: Set DRM_V3D=m

  * focal/linux-raspi: Upstream raspberrypi patchset 2020-05-11 (LP: #1877928)
- SAUCE: media: bcm2835-unicam: Resync to upstream raspberrypi
- media: bcm2835-unicam: Add support for mulitple device nodes.
- media: bcm2835-unicam: Add embedded data node.
- media: bcm2835-unicam: Use dummy buffer if none have been queued
- media: bcm2835-unicam: Disable event-related ioctls on metadata node
- media: bcm2835-unicam: Add support for the FRAME_SYNC event
- media: imx219: Advertise embedded data node on media pad 1
- dts: bcm2711: EMMC2 can address the whole first GB
- driver: char: rpivid: Remove legacy name support
- driver: char: rpivid: Don't map more than wanted
- defconfig: Enable I2C_MUX_PINCTRL in all Pi configs
- dt: Implement an I2C pinctrl mux for BSC0.
- dtoverlays: Update CSI overlays to use i2c_csi_dsi
- dt: Update all mainline bcm283x dt files for i2c0 pinctrl mux
- ARM: dts: Create bcm2708-rpi-b-rev1.dts
- dts: bcm2711: set #size-cells = <2>
- dts: bcm2711: add "High Peripheral" mode overlay
- Revert "spi: spidev: Fix CS polarity if GPIO descriptors are used"
- spi: use_gpio_descriptor fixup moved to spi_setup
- overlays: rpivid-v4l2 also needs size-cells = 2
- media: bcm2835-unicam: Re-fetch mbus code from subdev on a g_fmt call
- uapi: bcm2835-isp: Add bcm2835-isp uapi header file
- media: uapi: v4l2-core: Add ISP statistics output V4L2 fourcc type
- media: uapi: v4l-ctrls: Add CID base for the bcm2835-isp driver
- staging: mmal-vchiq: Fix formatting errors in mmal_parameters.h
- staging: vc04_services: ISP: Add a more complex ISP processing component
- staging: vchiq: Load bcm2835_isp driver from vchiq
- configs: Add VIDEO_ISP_BCM2835 to all Pi defconfigs
- vc4_hvs: Mark core clock as optional
- vc4_hdmi: BCM2835 requires a fixed hsm clock for CEC to work
- configs: Enable CONFIG_DRM_VC4_HDMI_CEC
- media: i2c: imx219: Implement get_selection
- media: i2c: ov5647: Add support for g_selection to reflect 
cropping/binning
- media: i2c: ov5467: Fixup error path to release mutex
- media: i2c: ov5647: Support V4L2_CID_PIXEL_RATE
- media: i2c: ov5647: Set V4L2_SUBDEV_FL_HAS_EVENTS flag
- media: i2c: ov5647: Add support for V4L2_CID_VBLANK
- media: i2c: ov5647: Neither analogue gain nor exposure need 
EXECUTE_ON_WRITE
- media: i2c: ov5647: Use member names in mode tables
- media: i2c: ov5647: Advertise the correct exposure range
- media: i2c: imx219: Declare that the driver can create events
- media: bcm2835-unicam: Add support for VIDIOC_[S|G]_SELECTION
- media: bcm2835-unicam: Do not stop streaming in unicam_release
- media: bcm2835-unicam: Fix reference counting in unicam_open
- staging: vc04_services: ISP: Add enum_framesizes ioctl
- SQUASH: spi: Demote SPI_CS_HIGH warning to KERN_DEBUG
- ARM: dts: bcm2711: Allow 40-bit DMA for SPI
- overlays: Make the i2c-gpio overlay safe again
- staging: vc04_services: isp: Remove duplicated initialisation
- staging: vc04_services: isp: Make all references to bcm2835_isp_fmt const
- overlays: gpio-keys: Avoid open-drain warnings
- configs: Add missing PPS configs
- configs: Add missing TOUCHSCREEN_RASPBERRYPI_FW=m
- vc4_hdmi_phy: Fix typo in phy_get_cp_current
- overlays: Make use of intra-overlay fragments
- media: i2c: tc358743: Fix fallthrough warning
- media: bcm2835: unicam: Fix uninitialized warning
- video: bcm2708_fb: Disable FB if no displays found
- overlays: sc16is752-spi1: Add xtal parameter
- vc4_hdmi: Fix register offset when sending longer CEC messages
- vc4_hdmi: Fix up CEC registers
- vc4_hdmi_regs: Add Intr2 register block
- vc4_hdmi_regs: Make interrupt mask variant specific
- vc4_hdmi: Make irq shared
- vc4_hdmi: Adjust CEC ref clock based on its input clock
- vc4_hdmi: Remove cec_available flag as always supported
- config: Enable CONFIG_DRM_VC4_HDMI_CEC
- [Config] raspi: updateconfigs after update to rpi-5.4.y

  [ Ubuntu: 5.4.0-34.38 ]

  * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118)
  * debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
  * Focal update: v5.4.41 upstream stable release (LP: #1878649)
- USB: 

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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1881120] Re: linux-oem-5.6-tools-common should be dropped

2020-06-10 Thread Timo Aaltonen
linux-oem-5.6 is fixed in git, linux still needs to add conflicts for
linux-oem-5.6-tools-common so it gets removed

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

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  linux-oem-5.6-tools-common should be dropped

Status in linux package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1882955] [NEW] LXD 4.2 broken on linux-kvm due to missing VLAN filtering

2020-06-10 Thread Stéphane Graber
Public bug reported:

This is another case of linux-kvm having unexplained differences
compared to linux-generic in areas that aren't related to hardware
drivers (see other bug we filed for missing nft).

This time, CPC is reporting that LXD no longer works on linux-kvm as we
now set vlan filtering on our bridges to prevent containers from
escaping firewalling through custom vlan tags.

This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the
generic kernel but is apparently missing on linux-kvm (I don't have any
system running that kernel to confirm its config, but the behavior
certainly matches that).

We need this fixed in focal and groovy.

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: Triaged

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

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

Title:
  LXD 4.2 broken on linux-kvm due to missing VLAN filtering

Status in linux-kvm package in Ubuntu:
  Triaged

Bug description:
  This is another case of linux-kvm having unexplained differences
  compared to linux-generic in areas that aren't related to hardware
  drivers (see other bug we filed for missing nft).

  This time, CPC is reporting that LXD no longer works on linux-kvm as
  we now set vlan filtering on our bridges to prevent containers from
  escaping firewalling through custom vlan tags.

  This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the
  generic kernel but is apparently missing on linux-kvm (I don't have
  any system running that kernel to confirm its config, but the behavior
  certainly matches that).

  We need this fixed in focal and groovy.

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

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


[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-10 Thread David Jeffrey
I have the same with the headset that was initially reported - the
Sennheiser HD 4.50 BTNC. A2DP works perfectly.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-riscv - 5.4.0-27.31

---
linux-riscv (5.4.0-27.31) focal; urgency=medium

  * focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798)

  * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667)
- [config] riscv: disable am-1805 RTC driver

  * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after
upgrade to 20.04 (LP: #1875665)
- [Config][focal/linux-riscv] Turn off CONFIG_RT_GROUP_SCHED

  [ Ubuntu: 5.4.0-34.38 ]

  * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118)
  * debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
  * Focal update: v5.4.41 upstream stable release (LP: #1878649)
- USB: serial: qcserial: Add DW5816e support
- nvme: refactor nvme_identify_ns_descs error handling
- nvme: fix possible hang when ns scanning fails during error recovery
- tracing/kprobes: Fix a double initialization typo
- net: macb: Fix runtime PM refcounting
- drm/amdgpu: move kfd suspend after ip_suspend_phase1
- drm/amdgpu: drop redundant cg/pg ungate on runpm enter
- vt: fix unicode console freeing with a common interface
- tty: xilinx_uartps: Fix missing id assignment to the console
- devlink: fix return value after hitting end in region read
- dp83640: reverse arguments to list_add_tail
- fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks
- ipv6: Use global sernum for dst validation with nexthop objects
- mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly
- neigh: send protocol value in neighbor create notification
- net: dsa: Do not leave DSA master with NULL netdev_ops
- net: macb: fix an issue about leak related system resources
- net: macsec: preserve ingress frame ordering
- net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc()
- net_sched: sch_skbprio: add message validation to skbprio_change()
- net: stricter validation of untrusted gso packets
- net: tc35815: Fix phydev supported/advertising mask
- net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict()
- net/tls: Fix sk_psock refcnt leak when in tls_data_ready()
- net: usb: qmi_wwan: add support for DW5816e
- nfp: abm: fix a memory leak bug
- sch_choke: avoid potential panic in choke_reset()
- sch_sfq: validate silly quantum values
- tipc: fix partial topology connection closure
- tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040
- bnxt_en: Fix VF anti-spoof filter setup.
- bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF.
- bnxt_en: Improve AER slot reset.
- bnxt_en: Return error when allocating zero size context memory.
- bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features().
- net/mlx5: DR, On creation set CQ's arm_db member to right value
- net/mlx5: Fix forced completion access non initialized command entry
- net/mlx5: Fix command entry leak in Internal Error State
- net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx()
- net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del()
- HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices
- sctp: Fix bundling of SHUTDOWN with COOKIE-ACK
- Revert "HID: wacom: generic: read the number of expected touches on a per
  collection basis"
- HID: usbhid: Fix race between usbhid_close() and usbhid_stop()
- HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT
- USB: uas: add quirk for LaCie 2Big Quadra
- usb: chipidea: msm: Ensure proper controller reset using role switch API
- USB: serial: garmin_gps: add sanity checking for data length
- tracing: Add a vmalloc_sync_mappings() for safe measure
- crypto: arch/nhpoly1305 - process in explicit 4k chunks
- KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction
- KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path
- KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER
- KVM: arm64: Fix 32bit PC wrap-around
- arm64: hugetlb: avoid potential NULL dereference
- drm: ingenic-drm: add MODULE_DEVICE_TABLE
- ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
- epoll: atomically remove wait entry on wake up
- eventpoll: fix missing wakeup for ovflist in ep_poll_callback
- mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous()
- mm: limit boost_watermark on small zones
- ceph: demote quotarealm lookup warning to a debug message
- staging: gasket: Check the return value of gasket_get_bar_index()
- coredump: fix crash when umh is disabled
- iocost: protect iocg->abs_vdebt with iocg->waitq.lock
- batman-adv: fix batadv_nc_random_weight_tq
- batman-adv: Fix refcnt leak in 

[Kernel-packages] [Bug 1877988] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

2020-06-10 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1881120 ***
https://bugs.launchpad.net/bugs/1881120

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1008.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i cannot install anything it crashes dpkg and cannot install any
  package from any repository by apt and dpkg

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   linux-tools-common:amd64: Install
   linux-tools-5.4.0-29:amd64: Install
   linux-tools-5.4.0-29-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1339 F pulseaudio
alireza2115 F pulseaudio
   /dev/snd/pcmC0D0p:   alireza2115 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon May 11 15:05:46 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ...
   Unpacking linux-tools-common (5.4.0-29.33) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1008.8
  InstallationDate: Installed on 2020-05-01 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81H7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=4ff62bed-a86c-4c62-a0fd-a29d1fd27022 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8QCN21WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 130-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8QCN21WW(V1.09):bd12/30/2019:svnLENOVO:pn81H7:pvrLenovoideapad130-15IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad130-15IKB:
  dmi.product.family: ideapad 130-15IKB
  dmi.product.name: 81H7
  dmi.product.sku: LENOVO_MT_81H7_BU_idea_FM_ideapad 130-15IKB
  dmi.product.version: Lenovo ideapad 130-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

2020-06-10 Thread AlekseyK
BIOS upgrade helped.

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1882893] [NEW] vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)

2020-06-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Recently, a couple of patches were upstreamed to Linux to upgrade
vmxnet3 driver to version 4. Below are the commits:

vmxnet3: prepare for version 4 changes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1

vmxnet3: add support to get/set rx flow hash
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794

vmxnet3: add geneve and vxlan tunnel offload support
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125

vmxnet3: update to version 4
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f

vmxnet3: use correct hdr reference when packet is encapsulated
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2

vmxnet3: allow rx flow hash ops only when rss is enabled
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8

This is a request to bring Ubuntu vmxnet3 driver up to date with Linux
kernel.

Thanks,
Yuhua Zou

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


** Tags: bot-comment
-- 
vmxnet3: update to latest vmxnet3 driver (upgrade vmxnet3 driver to version 4)
https://bugs.launchpad.net/bugs/1882893
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1882956] Re: Froze half-way through updating

2020-06-10 Thread Albert Cardona
I've now booted into linux 5.4.0-37-generic without incident.

** Description changed:

- In ubuntu 20.04 running linux kernel 5.4.0.31, running the updater
+ In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.
  
  To workaround, I rebooted, held the shift key and entered the grub menu,
  and booted using the prior kernel, linux 5.4.0.31. Then it worked. Grub
  was listing both linux 5.4.0.31 and linux 5.4.0.33, with the latter
- being the default and the one that froze upon booting.
+ being the default and the one that froze upon booting after the botched
+ update.
  
  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't yet
  tried to reboot into it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  albert 2075 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  albert 2075 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 14:58:58 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
  InstallationDate: Installed on 2016-06-24 (1446 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
-  Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
+  Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FQCTO1WW
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-31-generic N/A
-  linux-backports-modules-5.4.0-31-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-31-generic N/A
+  linux-backports-modules-5.4.0-31-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-20 (21 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

Title:
  Froze half-way through updating

Status in linux package in Ubuntu:
  New

Bug description:
  In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.

  To workaround, I rebooted, held the shift key and entered the grub
  menu, and booted using the prior kernel, linux 5.4.0.31. Then it
  worked. Grub was listing both linux 5.4.0.31 and linux 5.4.0.33, with
  the latter being the default and the one that froze upon booting after
  the botched update.

  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't
  yet tried to 

[Kernel-packages] [Bug 1882968] [NEW] ath10k_pci failed to wake target for write32

2020-06-10 Thread thedoctar
Public bug reported:

Wifi card stopped working. I use Lubuntu 20.04.

Wifi card info:

  *-network 
   description: Wireless interface
   product: QCA6174 802.11ac Wireless Network Adapter
   vendor: Qualcomm Atheros
   physical id: 0
   bus info: pci@:3a:00.0
   logical name: wlp58s0
   version: 32
   serial: 9c:b6:d0:d4:9b:33
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:135 memory:dc00-dc1f

Releveant journal log attached. In brief,

Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
...
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed

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

** Attachment added: "log.txt"
   https://bugs.launchpad.net/bugs/1882968/+attachment/5382474/+files/log.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/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed

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

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


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

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

apport-collect 1882968

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

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed

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

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


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

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

apport-collect 1882917

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1878484] Re: kernel panic on i915

2020-06-10 Thread Víctor Gonzalo
The kernel from #22 doesn't get to boot. Last message shown is a
suspicious:

fb0: switching to inteldrmfb from EFI VGA

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

Title:
  kernel panic on i915

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using 20.04 fully up to date on an Asrock N3700.

  I'm getting random crashes every now and then. Total crash, no ssh or
  anything (later I found out it's a kernel panic). Not tied to any app,
  but it happened more often during gaming. Logs didn't show anything,
  they just stop. I set up netconsole, with debug and ignore_loglevel in
  the command line and I got this:

  [77196.866485] BUG: unable to handle page fault for address: 00a72860
  [77196.866527] #PF: supervisor read access in kernel mode
  [77196.866535] #PF: error_code(0x) - not-present page
  [77196.866542] PGD 0 P4D 0 
  [77196.866552] Oops:  [#1] SMP PTI
  [77196.866567] CPU: 2 PID: 1408 Comm: Xorg Tainted: P   O  
5.4.0-29-generic #33-Ubuntu
  [77196.866575] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./N3700-ITX, BIOS P2.00 04/16/2018
  [77196.866743] RIP: 0010:__i915_schedule+0x261/0x350 [i915]
  [77196.866748] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 
49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 
60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00
  [77196.866753] RSP: 0018:a48380c2b9e0 EFLAGS: 00010006
  [77196.866759] RAX: 00a72800 RBX: 961bed909a30 RCX: 
9619a559edb0
  [77196.866764] RDX: 961bed909a50 RSI: 961beaa21180 RDI: 
9619a559edc0
  [77196.866769] RBP: a48380c2ba78 R08: 961bf73f4420 R09: 
9619a559ed80
  [77196.866773] R10:  R11: 0208 R12: 
961bf73f4000
  [77196.866783] R13: a48380c2b9f0 R14: 1000 R15: 
a48380c2b9c0
  [77196.866788] FS:  7f6ee2aa9a80() GS:961bf830() 
knlGS:
  [77196.866794] CS:  0010 DS:  ES:  CR0: 80050033
  [77196.866798] CR2: 00a72860 CR3: 00026a0a2000 CR4: 
001006e0
  [77196.866802] Call Trace:
  [77196.866887]  i915_schedule+0x2d/0x50 [i915]
  [77196.866979]  __fence_set_priority+0x6b/0x90 [i915]
  [77196.867067]  fence_set_priority+0x23/0x60 [i915]
  [77196.867117]  i915_gem_object_wait_priority+0x13e/0x170 [i915]
  [77196.867194]  intel_prepare_plane_fb+0x1ab/0x2d0 [i915]
  [77196.867232]  drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper]
  [77196.867305]  intel_atomic_commit+0xc2/0x2b0 [i915]
  [77196.867370]  drm_atomic_nonblocking_commit+0x4d/0x60 [drm]
  [77196.867401]  drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper]
  [77196.867443]  drm_mode_page_flip_ioctl+0x59d/0x630 [drm]
  [77196.867469]  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
  [77196.867490]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [77196.867512]  drm_ioctl+0x234/0x3d0 [drm]
  [77196.867536]  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
  [77196.867550]  do_vfs_ioctl+0x407/0x670
  [77196.867560]  ? fput+0x13/0x15
  [77196.867568]  ? __sys_recvmsg+0x88/0xa0
  [77196.867575]  ksys_ioctl+0x67/0x90
  [77196.867582]  __x64_sys_ioctl+0x1a/0x20
  [77196.867592]  do_syscall_64+0x57/0x190
  [77196.867603]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [77196.867611] RIP: 0033:0x7f6ee2e0737b
  [77196.867618] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48
  [77196.867624] RSP: 002b:7ffe6ff493d8 EFLAGS: 0246 ORIG_RAX: 
0010
  [77196.867631] RAX: ffda RBX: 7ffe6ff49410 RCX: 
7f6ee2e0737b
  [77196.867635] RDX: 7ffe6ff49410 RSI: c01864b0 RDI: 
000e
  [77196.867640] RBP: c01864b0 R08: 002bf8f2 R09: 
006a
  [77196.867645] R10: 000e R11: 0246 R12: 
56454c520040
  [77196.867649] R13: 000e R14: 002bf8f2 R15: 
0002
  [77196.867655] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel 
binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) 
spl(O) zlua(PO) joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr 
mei_hdcp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common 
intel_powerclamp coretemp kvm_intel kvm punit_atom_debug intel_cstate snd_seq 
snd_seq_device snd_timer snd mei_txe soundcore mei hci_uart 
intel_xhci_usb_role_switch btqca roles btrtl btbcm btintel bluetooth 
ecdh_generic ecc rfkill_gpio acpi_pad intel_int0002_vgpio mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt 

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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)

2020-06-10 Thread Ole Petersen
Hi, I have got basically the same machine, but the 14 inch version. My touchpad 
randomly works or not (about 50:50), but its behavior only changes after a 
second boot. If it does not work, I do constantly get the following kernel 
errors:
i2c_designware AMDI0010:00: controller timed out
Also, the touchpad is called sth like MSFT10010:00
and not Elan.
It's the same on all distros I tried (ubuntu, arch fedora)
Any 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/1881319

Title:
  Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as
  touch panel)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad isn't reacting at all

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andreas1223 F pulseaudio
   /dev/snd/controlC0:  andreas1223 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 29 18:05:01 2020
  InstallationDate: Installed on 2020-05-29 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: LENOVO 81YQ
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E7CN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
  dmi.product.family: IdeaPad 5 15ARE05
  dmi.product.name: 81YQ
  dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05
  dmi.product.version: IdeaPad 5 15ARE05
  dmi.sys.vendor: LENOVO

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

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

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread AlekseyK
apport information

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1081-oem N/A
   linux-backports-modules-4.15.0-1081-oem  N/A
   linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-06-10 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

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

Title:
  linux-oem-5.6-tools-common should be dropped

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2020-06-10 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Froze half-way through updating

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.

  To workaround, I rebooted, held the shift key and entered the grub
  menu, and booted using the prior kernel, linux 5.4.0.31. Then it
  worked. Grub was listing both linux 5.4.0.31 and linux 5.4.0.33, with
  the latter being the default and the one that froze upon booting after
  the botched update.

  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't
  yet tried to reboot into it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2075 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 14:58:58 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
  InstallationDate: Installed on 2016-06-24 (1446 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FQCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-20 (21 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1877120] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

2020-06-10 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1881120 ***
https://bugs.launchpad.net/bugs/1881120

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1008.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installation Error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   1251 F pulseaudio
gdm1284 F pulseaudio
dhairy 1852 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed May  6 19:12:36 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ...
   Unpacking linux-tools-common (5.4.0-29.33) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1008.8
  InstallationDate: Installed on 2020-04-23 (12 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Dell Inc. Inspiron 5577
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6e08e244-ff74-4758-8edd-bddfdce5aecf ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  UpgradeStatus: Upgraded to focal on 2020-04-23 (12 days ago)
  dmi.bios.date: 12/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.2
  dmi.board.name: 0MVD5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.2:bd12/01/2018:svnDellInc.:pnInspiron5577:pvr1.1.2:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5577
  dmi.product.sku: 07E1
  dmi.product.version: 1.1.2
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

2020-06-10 Thread AlekseyK
** Description changed:

- Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
+ Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec
  
  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists: after
  I close laptop cover or after some time of inactivity Ubuntu suspends or
  hibernate (do not know). After I resume it, it starts to work but in
  10-15 sec Ubuntu freezes and I forced to power-off.
  
  Tried many things mentioned here:
  
  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc
  
  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original nvidia
  driver from manufacturer site. Do not know however if it affects
  warranty? ;) Any ideas how to solve, how to diagnose? Thanks!
  
  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):
  
  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)
  
  Logs for 4.18 kernel are slightly different:
  
  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)
  
- 
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  aleksey8485 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aleksey8485 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-04 (158 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 5501
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_UA.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_UA.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-1081-oem N/A
-  linux-backports-modules-4.15.0-1081-oem  N/A
-  linux-firmware   1.173.18
+  linux-restricted-modules-4.15.0-1081-oem N/A
+  linux-backports-modules-4.15.0-1081-oem  N/A
+  linux-firmware   1.173.18
  Tags:  bionic
  Uname: Linux 4.15.0-1081-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.4
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.sys.vendor: Dell Inc.

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked here as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends 

[Kernel-packages] [Bug 1882956] [NEW] Froze half-way through updating

2020-06-10 Thread Albert Cardona
Public bug reported:

In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
resulted in a frozen, irresponsive mouse and keyboard, and the laptop
wouldn't suspend when closing the lid. Upon reboot, the laptop froze
before reaching the login screen.

To workaround, I rebooted, held the shift key and entered the grub menu,
and booted using the prior kernel, linux 5.4.0.31. Then it worked. Grub
was listing both linux 5.4.0.31 and linux 5.4.0.33, with the latter
being the default and the one that froze upon booting after the botched
update.

Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
installation. ```sudo dpkg --configure -a``` solved the issue without
incident, updating grub with a new entry for linux 5.4.0.37. Haven't yet
tried to reboot into it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  albert 2075 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 14:58:58 2020
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
InstallationDate: Installed on 2016-06-24 (1446 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera
 Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FQCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-05-20 (21 days ago)
dmi.bios.date: 04/18/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET40W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 1st
dmi.product.name: 20FQCTO1WW
dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
dmi.product.version: ThinkPad X1 Yoga 1st
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Froze half-way through updating

Status in linux package in Ubuntu:
  New

Bug description:
  In ubuntu 20.04 running linux kernel 5.4.0.33, running the updater
  resulted in a frozen, irresponsive mouse and keyboard, and the laptop
  wouldn't suspend when closing the lid. Upon reboot, the laptop froze
  before reaching the login screen.

  To workaround, I rebooted, held the shift key and entered the grub
  menu, and booted using the prior kernel, linux 5.4.0.31. Then it
  worked. Grub was listing both linux 5.4.0.31 and linux 5.4.0.33, with
  the latter being the default and the one that froze upon booting after
  the botched update.

  Upon booting to linux 5.4.0.31, apt-get reported an unfinished package
  installation. ```sudo dpkg --configure -a``` solved the issue without
  incident, updating grub with a new entry for linux 5.4.0.37. Haven't
  yet tried to reboot into it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert 2075 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 14:58:58 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=394271b7-2e0e-42af-b70b-cffbb608ed13
  InstallationDate: Installed on 2016-06-24 (1446 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated 

[Kernel-packages] [Bug 1881644] Re: 20.04 i915 laptop external monitor doesn't resume from power-save, must open lid to turn it on

2020-06-10 Thread Bjorn Helgaas
I'm not using Mint.  I started with Ubuntu 18.04 in June 2018, installed
the "cinnamon" package, and recently updated to 20.04.  I don't know if
this is a regression because I didn't start using this configuration
until after moving to 20.04.  Pretty sure cinnamon came from the ubuntu
repo; my only apt sources change is for chrome.

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

Title:
  20.04 i915 laptop external monitor doesn't resume from power-save,
  must open lid to turn it on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell 5520 laptop -> Dell Thunderbolt dock -> HDMI -> external monitor.
  Running 20.04, i915 driver.

  Laptop lid closed, using external monitor only.  When external monitor
  turns off (after sleep-display-ac), keyboard/mouse activity should
  turn it back on, but do not.  Opening and closing the laptop lid does
  turn the external monitor back on.  Laptop is not suspended; I can ssh
  in from another machine.

  Happy to collect any additional information.

  To reproduce:
  - On Dell 5520 laptop connected to Dell Thunderbolt dock connected to 
external monitor via HDMI
  - Close laptop lid
  - Use external monitor, external keyboard, external mouse
  - Leave system idle for "sleep-display-ac" time
  - System puts external monitor in power-save mode
  - Move mouse, type on keyboard
  - No response, external monitor remains in power-save mode
  - Open laptop lid
  - External monitor turns on
  - Close laptop lid
  - External monitor remains on, I'm able to work as usual
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bjorn  1993 F pulseaudio
   /dev/snd/controlC1:  bjorn  1993 F pulseaudio
   /dev/snd/controlC0:  bjorn  1993 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=39f2962e-3115-438f-a447-03558db08edb
  InstallationDate: Installed on 2018-06-08 (725 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Precision 5520
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-29 (34 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 1203147
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

2020-06-10 Thread AlekseyK
apport information

** Tags added: apport-collected bionic

** Description changed:

  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec
  
  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists: after
  I close laptop cover or after some time of inactivity Ubuntu suspends or
  hibernate (do not know). After I resume it, it starts to work but in
  10-15 sec Ubuntu freezes and I forced to power-off.
  
  Tried many things mentioned here:
  
  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc
  
  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original nvidia
  driver from manufacturer site. Do not know however if it affects
  warranty? ;) Any ideas how to solve, how to diagnose? Thanks!
  
  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):
  
  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)
  
  Logs for 4.18 kernel are slightly different:
  
  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)
+ 
+ 
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.15
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  aleksey8485 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+brookhollow+X77
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-01-04 (158 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
+ MachineType: Dell Inc. Latitude 5501
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_UA.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=cbf51edd-c7a5-4b05-96bb-e7e5f227e70a ro nvidia-drm.modeset=1 
nouveau.blacklist=1 mem_sleep_default=deep quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-1081-oem N/A
+  linux-backports-modules-4.15.0-1081-oem  N/A
+  linux-firmware   1.173.18
+ Tags:  bionic
+ Uname: Linux 4.15.0-1081-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/12/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.8.4
+ dmi.board.name: 0Y8H01
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.4:bd05/12/2020:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 5501
+ dmi.sys.vendor: Dell Inc.

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it 

[Kernel-packages] [Bug 1882008] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

2020-06-10 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1881120 ***
https://bugs.launchpad.net/bugs/1881120

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1008.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  terminal says to "apt --fix broken install" doing that doesnt work

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shaswat1593 F pulseaudio
   /dev/snd/controlC0:  shaswat1593 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun  4 09:48:47 2020
  DpkgHistoryLog:
   Start-Date: 2020-06-04  09:48:45
   Commandline: apt --fix-broken install
   Requested-By: shaswat (1000)
   Install: linux-tools-common:amd64 (5.4.0-33.37, automatic)
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-33.37_all.deb ...
   Unpacking linux-tools-common (5.4.0-33.37) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-33.37_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1008.8
  InstallationDate: Installed on 2020-05-06 (28 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire E1-472
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=315e55da-ed68-4b87-882f-3732bfb41034 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1008.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.08
  dmi.board.name: EA40_HW
  dmi.board.vendor: Acer
  dmi.board.version: V2.08
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.08
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.08:bd10/14/2013:svnAcer:pnAspireE1-472:pvrV2.08:rvnAcer:rnEA40_HW:rvrV2.08:cvnAcer:ct9:cvrV2.08:
  dmi.product.family: Aspire E1-472
  dmi.product.name: Aspire E1-472
  dmi.product.sku: Aspire E1-472_0762_2.08
  dmi.product.version: V2.08
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1882895] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

2020-06-10 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1881120 ***
https://bugs.launchpad.net/bugs/1881120

** This bug has been marked a duplicate of bug 1881120
   linux-oem-5.6-tools-common should be dropped

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1010.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a bad one.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  squinton   1113 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 09:18:45 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-37.41_all.deb ...
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  DuplicateSignature:
   package:linux-tools-common:(not installed)
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1010.10
  InstallationDate: Installed on 2020-05-09 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 004: ID 05ac:024f Apple, Inc. 
   Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.9
  dmi.board.name: 0HD5W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1881120] Re: linux-oem-5.6-tools-common should be dropped

2020-06-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  linux-oem-5.6-tools-common should be dropped

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1864132] Re: g_ether missing eem support

2020-06-10 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1861070 ***
https://bugs.launchpad.net/bugs/1861070

** This bug has been marked a duplicate of bug 1861070
   Raspberry Pi 4B: USB OTG is not working

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

Title:
  g_ether missing eem support

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  New

Bug description:
  I am looking into enabling EEM with g_ether by module option
  use_eem=1, and g_ether won't be loaded because it has no EEM support
  compiled.

  Expected: EEM is compiled with g_ether (no such option for g_cdc) so
  that it can be enabled by use_eem=1.

  My "/sys/module/g_ether/parameters":
  -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice
  -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr
  -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct
  -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber
  -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct
  -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor
  -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult

  modinfo g_ether:
  parm:   idVendor:USB Vendor ID (ushort)
  parm:   idProduct:USB Product ID (ushort)
  parm:   bcdDevice:USB Device version (BCD) (ushort)
  parm:   iSerialNumber:SerialNumber string (charp)
  parm:   iManufacturer:USB Manufacturer string (charp)
  parm:   iProduct:USB Product string (charp)
  parm:   qmult:queue length multiplier at high/super speed (uint)
  parm:   dev_addr:Device Ethernet Address (charp)
  parm:   host_addr:Host Ethernet Address (charp)
  parm:   use_eem:use CDC EEM mode (bool)

  dmesg:
  ...
  [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to 
list of pending drivers
  ...
  [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in 
SPRAM
  [5.772414] g_ether fe98.usb: failed to start g_ether: -2
  ...

   should it be another bug? -
  There is another issue that when my laptop is connected and the with my Pi 4 
reboot, the cdc_ether function provided to my laptop will not be available 
again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can 
unplug on laptop side w/o Pi 4 losing power).  I remember it was working as 
expected when I was testing out OTG function.

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

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


[Kernel-packages] [Bug 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28

2020-06-10 Thread PhilX
The bug still exists with 5.3.0-59 and also with the newest Ubuntu 20.04
LTS (kernel 5.4). No mouse and keyboard is working. Why is no one
reacting to such an massive bug, where a lot of people can't use Ubuntu
any more?

** Also affects: linux-signed-hwe (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  USB system (mouse and keybord) are not working since kernel update to
  5.3.0-26 and 5.3.0-28

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  New

Bug description:
  Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. 
Keyboard and mouse (both connected via USB) are not working. It looks like 
everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the 
new kernel version has problems with the USB system. If I choose in GRUB an 
older kernel version (e.g. 5.0.0-37) everything is fine.
  Same problem with kernel 5.3.0-28.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Feb 16 05:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2019-03-19 (333 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: MSI MS-7817
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Kernel-packages] [Bug 1871977] Re: g_ether not working after reboot

2020-06-10 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1861070 ***
https://bugs.launchpad.net/bugs/1861070

** This bug has been marked a duplicate of bug 1861070
   Raspberry Pi 4B: USB OTG is not working

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

Title:
  g_ether not working after reboot

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  New
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  There is an issue with g_ether after warm reboot.

  Hardware I used for testing:

  Thinkpad L470 + Dock, Ubuntu 19.10
  USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter
  Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu 
19.10

  ==
  it seems like whenever I reboot my Pi, USB gadget port is not detected.  How 
to reproduce:

  1) make sure g_ether works on Pi 4
  2) make sure cdc_ether works on L470, as in dmesg it shows...
  [112961.147030] usb 1-3.2: new high-speed USB device number 11 using xhci_hcd
  [112961.237399] usb 1-3.2: New USB device found, idVendor=045e, 
idProduct=0301, bcdDevice= 5.03
  [112961.237406] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [112961.237411] usb 1-3.2: Product: USB Adapter
  [112961.237414] usb 1-3.2: Manufacturer: Raspberry Pi
  [112961.237418] usb 1-3.2: SerialNumber: ***MASKED***
  [112961.245067] cdc_ether 1-3.2:1.0 eth1: register 'cdc_ether' at 
usb-:00:14.0-3.2, CDC Ethernet Device, ***MASKED***
  3) verify IP connectivity works from L470 to Pi 4.
  4) reboot Pi 4; on L470 it shows:
  [113343.783925] usb 1-3.2: USB disconnect, device number 11
  [113343.784164] cdc_ether 1-3.2:1.0 eth1: unregister 'cdc_ether' 
usb-:00:14.0-3.2, CDC Ethernet Device
  5) wait for Pi 4 to become available (I use wifi on Pi 4 + ssh on L470)
  ==

  Expected: Pi4 should show up to L470 as USB ethernet gadget after warm reboot
  Actual: g_ether is loaded on Pi4 but L470 does not detect it
  Workaround: unplug Pi4 and plug in again, it will work;  given that I am 
using Y-cable, unplugging will not power down Pi 4.
  Concern: lose connectivity that needs human intervention to correct, i.e. 
cannot do it remotely.

  Note: I remember it is detected okay before I file for bug #1861070,
  not sure if it is related or not.  using g_cdc should be the same, but
  not separately tested.

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

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


[Kernel-packages] [Bug 1882896] [NEW] cheese not recognize resolution in MJPG format

2020-06-10 Thread Alex Tu
Public bug reported:

reproduce step:
 - open cheese
 - open preferences -> resolution
 - only resolution from YUYV format in options

the patches there works well and waiting for merge:
https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cheese 3.34.0-1build1
ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
Uname: Linux 5.6.0-1008-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 10 15:23:02 2020
InstallationDate: Installed on 2020-04-12 (58 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
MachineType: Dell Inc. XPS 13 9380
RelatedPackageVersions:
 cheese3.34.0-1build1
 cheese-common 3.34.0-1build1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.

** Affects: cheese
 Importance: Unknown
 Status: Unknown

** Affects: oem-priority
 Importance: High
 Status: New

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


** Tags: amd64 apport-bug focal gstreamer-error oem-priority 
originate-from-1881688 somerville

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

Title:
  cheese not recognize resolution in MJPG format

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  reproduce step:
   - open cheese
   - open preferences -> resolution
   - only resolution from YUYV format in options

  the patches there works well and waiting for merge:
  https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1build1
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:23:02 2020
  InstallationDate: Installed on 2020-04-12 (58 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  RelatedPackageVersions:
   cheese3.34.0-1build1
   cheese-common 3.34.0-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1882890] Re: Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

2020-06-10 Thread Jérôme
I forced a downgrade of intel-microcode from "" to "", regenerated the
initrd images, and now they seems to boot correctly!

So, the problem seems to be with latest intel-microcode?

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

Title:
  Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This morning I applied the latest updates on my Ubuntu 16.04 (kernel
  4.15.0-106-generic + intel-microcode 3.20200609.0ubuntu0.16.04.0) and
  rebooted as usual to boot on the new kernel but the system won't boot:
  black screen.

  I tried booting the previous kernel 4.15.0-101 and it seems to be the
  same : in grub I select the 4.15.0-101 kernel, press enter, a message
  "Loading initrd..." is printed but nothing else happens.

  Tried even older kenrel 4.4.0-184-generic : same problem, "Loading
  initrd...", and nothing happens.

  I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-
  functionnal.

  I mounted the /boot partition from a USB rescue drive, and it seems that all 
the initrd images that got updated this morning are not bootable anymore :
  - initrd.img-4.15.0-106-generic
  - initrd.img-4.15.0.101-generic
  - initrd.img-4.4.0-184-generic

  I tried regenerating the images with update-initramfs but it's the
  same : "Loading initrd" message but nothing happens.

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

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


[Kernel-packages] [Bug 1880975] Re: Request to include two NUMA related commits in Azure kernels

2020-06-10 Thread Stefan Bader
** Also affects: linux-azure (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: linux-azure (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux-azure (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: linux-azure (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: linux-azure (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Focal)
   Status: New => Triaged

** Changed in: linux-azure (Ubuntu)
   Status: New => Invalid

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

Title:
  Request to include two NUMA related commits in Azure kernels

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Triaged
Status in linux-azure source package in Eoan:
  Triaged
Status in linux-azure source package in Focal:
  Triaged

Bug description:
  Microsoft would like to request the following two commits in all
  releases supported on Azure:

  999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support 
PCI_BUS_RELATIONS2")
  f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP 
message")

  These two commits will add support for PCI protocol version 1.3.  This
  will allow the host to pass NUMA node information for devices on the
  bus.  Currently it is assumed the NUMA node is 0, which these patches
  will correct.  This functionality will provide an increase in
  performance, especially for HPC and AI workloads.

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

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


[Kernel-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format

2020-06-10 Thread Kai-Heng Feng
** Package changed: linux (Ubuntu) => cheese (Ubuntu)

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

Title:
  cheese not recognize resolution in MJPG format

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  New
Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  reproduce step:
   - open cheese
   - open preferences -> resolution
   - only resolution from YUYV format in options

  the patches there works well and waiting for merge:
  https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1build1
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:23:02 2020
  InstallationDate: Installed on 2020-04-12 (58 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  RelatedPackageVersions:
   cheese3.34.0-1build1
   cheese-common 3.34.0-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1876885] Re: linux: riscv: set max_pfn to the PFN of the last page

2020-06-10 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  linux: riscv: set max_pfn to the PFN of the last page

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  == SRU Justification Focal/Groovy ==

  The current max_pfn equals to zero. In this case, I found it caused users
  cannot get some page information through /proc such as kpagecount in v5.6
  kernel because of new sanity checks. The following message is displayed by
  stress-ng test suite with the command "stress-ng --verbose --physpage 1 -t
  1" on HiFive unleashed board.

   # stress-ng --verbose --physpage 1 -t 1
   stress-ng: debug: [109] 4 processors online, 4 processors configured
   stress-ng: info: [109] dispatching hogs: 1 physpage
   stress-ng: debug: [109] cache allocate: reducing cache level from L3 (too 
high) to L0
   stress-ng: debug: [109] get_cpu_cache: invalid cache_level: 0
   stress-ng: info: [109] cache allocate: using built-in defaults as no 
suitable cache found
   stress-ng: debug: [109] cache allocate: default cache size: 2048K
   stress-ng: debug: [109] starting stressors
   stress-ng: debug: [109] 1 stressor spawned
   stress-ng: debug: [110] stress-ng-physpage: started [110] (instance 0)
   stress-ng: error: [110] stress-ng-physpage: cannot read page count for 
address 0x3fd34de000 in /proc/kpagecount, errno=0 (Success)
   stress-ng: error: [110] stress-ng-physpage: cannot read page count for 
address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success)
   ...
   stress-ng: error: [110] stress-ng-physpage: cannot read page count for 
address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success)
   stress-ng: debug: [110] stress-ng-physpage: exited [110] (instance 0)
   stress-ng: debug: [109] process [110] terminated
   stress-ng: info: [109] successful run completed in 1.00s
   #

  == Fix ==

  Upstream commit in linux-next:

  commit c749bb2d554825e007cbc43b791f54e124dadfce
  Author: Vincent Chen 
  Date:   Mon Apr 27 14:59:24 2020 +0800

  riscv: set max_pfn to the PFN of the last page

  == Test Case ==

  Without the patch, running stress-ng --verbose --physpage 1 -t
  1 on HiFive unleashed board will trip the bug.  With the patch, the test 
passes as follows:

   # stress-ng --verbose --physpage 1 -t 1
   stress-ng: debug: [104] 4 processors online, 4 processors configured 
stress-ng: info: [104] dispatching hogs: 1 physpage
   stress-ng: info: [104] cache allocate: using defaults, can't determine cache 
details from sysfs
   stress-ng: debug: [104] cache allocate: default cache size: 2048K
   stress-ng: debug: [104] starting stressors
   stress-ng: debug: [104] 1 stressor spawned
   stress-ng: debug: [105] stress-ng-physpage: started [105] (instance 0) 
stress-ng: debug: [105] stress-ng-physpage: exited [105] (instance 0) 
stress-ng: debug: [104] process [105] terminated
   stress-ng: info: [104] successful run completed in 1.01s
   

  == Regression Potential ==

  Small, this correctly fixes the max_pfn and max_low_pfn to the correct
  end of DRAM location.  The fix now can be shown to set these
  appropriately because stress-ng no longer triggers this corner case.

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

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


[Kernel-packages] [Bug 1881810] Re: ZFS import cause panic

2020-06-10 Thread Colin Ian King
Looks like you may have data corruption.  One can temporarily disable
the spa verification to see if this allows the import to at least
complete to see if this helps.

echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_metadata
echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_data

do the import, and then re-enable:

echo 1 | sudo tee /sys/module/zfs/parameters/spa_load_verify_metadata
echo 1 | sudo tee /sys/module/zfs/parameters/spa_load_verify_data

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

Title:
  ZFS import cause panic

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  1)
  Ubuntu 20.04 LTS

  2)
  apt policy zfsutils-linux
  zfsutils-linux:
  Installed: 0.8.3-1ubuntu12
  Candidate:0.8.3-1ubuntu12

  3)
  ZFS pool not possible to import, unless using read only.
  If trying to import normal way as write/read, casing panic message

  Expected to be able to import zpool without panic.
  Expected that scrub should not be able to run in read only.
  Expected that somehow be able to restore the zpool somehow.


  
  4)
  # zpool status
  no pools available
  # zpool import
 pool: datastore
   id: 3190464655986727485
state: ONLINE
   status: Some supported features are not enabled on the pool.
   action: The pool can be imported using its name or numeric identifier, though
  some features will not be available without an explicit 'zpool 
upgrade'.
   config:

  datastore   ONLINE
raidz2-0  ONLINE
  sdb ONLINE
  sdc ONLINE
  sdd ONLINE
  sde ONLINE
  sdf ONLINE
  sdg ONLINE

  # zpool import -o readonly=on datastore
  # zpool status
pool: datastore
   state: ONLINE
  status: Some supported features are not enabled on the pool. The pool can
  still be used, but some features are unavailable.
  action: Enable all features using 'zpool upgrade'. Once this is done,
  the pool may no longer be accessible by software that does not support
  the features. See zpool-features(5) for details.
scan: scrub in progress since Sun May 10 00:24:01 2020
  15,1T scanned at 0B/s, 15,1T issued at 0B/s, 15,1T total
  1,44M repaired, 100,01% done, no estimated completion time
  config:

  NAMESTATE READ WRITE CKSUM
  datastore   ONLINE   0 0 0
raidz2-0  ONLINE   0 0 0
  sdb ONLINE   0 0 0
  sdc ONLINE   0 0 0
  sdd ONLINE   0 0 0
  sde ONLINE   0 0 0
  sdf ONLINE   0 0 0
  sdg ONLINE   0 0 0

  errors: No known data errors

  
  Running zdb it always stops ad 2,23T and then aborts.
  # zdb -e -bcsvL datastore
  Traversing all blocks to verify checksums ...
  2.23T completed ( 149MB/s) estimated time remaining: 25hr 06min 25sec
free(): invalid pointer
  Abort (SIGABRT)

  
  #zpool import datastore
  VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (36028797018963967 
< 32768)
  PANIC at zio.c:293:zio_buf_alloc()

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

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


[Kernel-packages] [Bug 1635115] Re: grub fails zfs root filesystem detection due to failed checksum

2020-06-10 Thread Marcos Alano
I'm having the same problem with Ubuntu 20.4 after update my kernel.

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

Title:
  grub fails zfs root filesystem detection due to failed checksum

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  root@q-1-d.sv1:~# lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  root@q-1-d.sv1:~# apt-cache policy grub2-common
  grub2-common:
Installed: 2.02~beta2-36ubuntu3.2
Candidate: 2.02~beta2-36ubuntu3.2
Version table:
   *** 2.02~beta2-36ubuntu3.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.02~beta2-36ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  I followed https://github.com/zfsonlinux/zfs/wiki/Ubuntu-16.04-Root-on-ZFS to 
make a ZFS native root disk system.  

  Installation went fine, systems works like a champ... but then, after
  a while, it's time to apt-get update ; apt-get upgrade to update my
  kernel.  That apt-get install fails because grub can't detect it's
  root file system:

  root@q-2-d.sv1:~# grub-probe /
  grub-probe: error: unknown filesystem.

  Strange, this use to work.  Add in a -vv and I see:

  grub-core/kern/fs.c:56: Detecting zfs...
  grub-core/osdep/hostdisk.c:415: opening the device `/dev/sda1' in 
open_device()
  grub-core/fs/zfs/zfs.c:1192: label ok 0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:1007: check 2 passed
  grub-core/fs/zfs/zfs.c:1018: check 3 passed
  grub-core/fs/zfs/zfs.c:1025: check 4 passed
  grub-core/fs/zfs/zfs.c:1035: check 6 passed
  grub-core/fs/zfs/zfs.c:1043: check 7 passed
  grub-core/fs/zfs/zfs.c:1054: check 8 passed
  grub-core/fs/zfs/zfs.c:1064: check 9 passed
  grub-core/fs/zfs/zfs.c:1086: check 11 passed
  grub-core/fs/zfs/zfs.c:1112: check 10 passed
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:hole_birth
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:embedded_data
  grub-core/fs/zfs/zfs.c:1137: check 12 passed (feature flags)
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 2048/2048
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, b00258
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:442: checksum fletcher4 verification failed
  grub-core/fs/zfs/zfs.c:447: actual checksum 0059d95adad1 6322fba304b3 
00430f321ad7f439 21e873b51c15e3bc
  grub-core/fs/zfs/zfs.c:452: expected checksum 00035ca143fb 
062fc3a48ff8 0005b49e0d96b07e 03841abf1fed586a
  grub-core/fs/zfs/zfs.c:1919: incorrect checksum
  grub-core/kern/fs.c:78: zfs detection failed.

  Now here's the fun part.  Rebooting the system will fix the checksum
  issue for a short amount of time.  Here is what it looks like
  immediately after a reboot:

  root@q-1-d.sv1:~# grub-probe /
  zfs

  grub-core/kern/fs.c:56: Detecting zfs...
  grub-core/osdep/hostdisk.c:415: opening the device `/dev/sda1' in 
open_device()
  grub-core/fs/zfs/zfs.c:1192: label ok 0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:1007: check 2 passed
  grub-core/fs/zfs/zfs.c:1018: check 3 passed
  grub-core/fs/zfs/zfs.c:1025: check 4 passed
  grub-core/fs/zfs/zfs.c:1035: check 6 passed
  grub-core/fs/zfs/zfs.c:1043: check 7 passed
  grub-core/fs/zfs/zfs.c:1054: check 8 passed
  grub-core/fs/zfs/zfs.c:1064: check 9 passed
  grub-core/fs/zfs/zfs.c:1086: check 11 passed
  grub-core/fs/zfs/zfs.c:1112: check 10 passed
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:hole_birth
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:embedded_data
  grub-core/fs/zfs/zfs.c:1137: check 12 passed (feature flags)
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 2048/2048
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001c0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:2678: endian = -1, blkid=0
  grub-core/fs/zfs/zfs.c:2020: endian = -1
  grub-core/fs/zfs/zfs.c:2051: endian = -1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001b8
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:2020: endian = 1
  grub-core/fs/zfs/zfs.c:2046: endian = 1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian = 1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001a0
  grub-core/fs/zfs/zfs.c:2682: alive
  grub-core/fs/zfs/zfs.c:2493: looking for 'features_for_read'
  grub-core/fs/zfs/zfs.c:2020: endian = 1
  grub-core/fs/zfs/zfs.c:2046: endian = 1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: 

[Kernel-packages] [Bug 1882944] [NEW] Resolution and settings changed

2020-06-10 Thread BJ Steeves
Public bug reported:

Resolution was set to 640x800 and not able to change it. Monitor and
graphics drivers not recognized. All display settings changed and not
correctable.

Rebooted back to the 5.3 kernel and system is back to normal.

May delete the 5.4 kernel until corrected.

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

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

Title:
  Resolution and settings changed

Status in linux package in Ubuntu:
  New

Bug description:
  Resolution was set to 640x800 and not able to change it. Monitor and
  graphics drivers not recognized. All display settings changed and not
  correctable.

  Rebooted back to the 5.3 kernel and system is back to normal.

  May delete the 5.4 kernel until corrected.

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

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


[Kernel-packages] [Bug 1870769] Re: System slow/freezing when copying files (Kernel 5.4.x)

2020-06-10 Thread gunessee
Issue got fixed in subsequent kernel patches.
Please close the 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/1870769

Title:
  System slow/freezing when copying files (Kernel 5.4.x)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While coping files (more noticeable when copying/moving large files), the 
freezes randomly. Cursor freezes as well.  
  After all files have been copied/moved, the system then behaves normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1844 F pulseaudio
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 10:43:31 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Acer Swift SF314-56
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.name: Strongbow_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd08/12/2019:svnAcer:pnSwiftSF314-56:pvrV1.14:rvnWL:rnStrongbow_WL:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-56
  dmi.product.sku: 
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1837898] Re: zfs-linux 0.8.1-1ubuntu7 ADT test failure with linux 5.3.0-0.1

2020-06-10 Thread Colin Ian King
This is working now, marking as fixed released.

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

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zfs-linux 0.8.1-1ubuntu7 ADT test failure with linux 5.3.0-0.1

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/z/zfs-linux/20190724_125958_497a5@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/z/zfs-linux/20190724_140254_497a5@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/z/zfs-linux/20190724_125902_497a5@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/z/zfs-linux/20190724_133756_497a5@/log.gz

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

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


[Kernel-packages] [Bug 1882936] [NEW] [Ubuntu 20.10] Secure Boot Testing for Ubuntu 20.10 with test kernel

2020-06-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

x

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


** Tags: architecture-s39064 bugnameltc-186168 severity-high 
targetmilestone-inin2010
-- 
[Ubuntu 20.10] Secure Boot Testing for Ubuntu 20.10 with test kernel
https://bugs.launchpad.net/bugs/1882936
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries

2020-06-10 Thread Guilherme G. Piccoli
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Bionic ubuntu ethtool doesn't check ring parameters boundaries

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  * There's a bad behavior in the ena driver ringparam setting on kernels 4.4 
and 4.15, if an invalid ringparam is provided to ethtool.

  * Upstream Linux kernel implemented ring parameter boundaries check in 
commit: 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds 
during SRINGPARAM") [ git.kernel.org/linus/37e2d99b59c4 ].
  Due to this commit, the community doesn't usually allow ring parameter 
boundary checks in driver code.

  * Xenial/Bionic kernels don't include this patch, and some network
  drivers (like ena) rely on this patch for boundary checking of ring
  params. So, we are hereby requesting the commit inclusion in these
  kernel versions.

  [Test case]
  1. In AWS, create a new c5.4xlarge instance with the Ubuntu 18.04 official 
ami (uses the ENA network driver) and update to latest kernel/reboot.

  2. Run ethtool -g ens5
  output:
  Ring parameters for ens5:
  Pre-set maximums:
  RX:   16384
  RX Mini:  0
  RX Jumbo: 0
  TX:   1024
  Current hardware settings:
  RX:   1024
  RX Mini:  0
  RX Jumbo: 0
  TX:   1024

  3. Change the TX/RX ring size to a legal number within boundaries -
  works!

  4. Change the TX/RX ring size to an illegal number (such as 2048 for
  TX) with the command - "sudo ethtool -G ens5 tx 2048".

  Expected behavior - "Cannot set device ring parameters: Invalid argument"
  Actual behavior - causes a driver hang since boundaries are not checked by 
ethtool, effectively hanging the instance (given that AWS has no console to 
allow system manipulation).

  [Regression Potential]

  Since that the commit is present in kernels v4.16+ (including Ubuntu)
  and is quite small and self-contained, the regression risk is very
  reduced.

  One potential "regression" would be if some driver has bugs and
  provide bad values on get_ringparams, then the validation would be
  broken (allowing illegal values or refusing legal ones), but this
  wouldn't be a regression in the hereby proposed patch itself, it'd be
  only exposed by the patch.

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

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


[Kernel-packages] [Bug 1882917] [NEW] Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

2020-06-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
freezes-after-resume-from-suspend-hibernate-in-10-15-sec

Bought new laptop - [Dell
Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
with Ubuntu 18.04.4. Works fine, however the only problem exists: after
I close laptop cover or after some time of inactivity Ubuntu suspends or
hibernate (do not know). After I resume it, it starts to work but in
10-15 sec Ubuntu freezes and I forced to power-off.

Tried many things mentioned here:

- blacklist nouveau
- install older kernel - 4.14.41
- update to newer - 4.18 or latest 5.3 kernel
- switch to proprietary nvidia driver (was installed by default)
- install `lightdm` instead of `gdm3`
- dell software had run some recent firmware upgrade
- etc

Nothing work - it still freezes and it is impossible to work. The only
suggestion I did not tried yet: install kubuntu and then original nvidia
driver from manufacturer site. Do not know however if it affects
warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

System, hardware and security logs during suspend/resume attached
(original 4.15 kernel):

- [System.log](https://pastebin.com/0Ttnu7T9)
- [Security.log](https://pastebin.com/Wme1y1wM)
- [Hardware.log](https://pastebin.com/ujUS5Ce4)

Logs for 4.18 kernel are slightly different:

- [System_4.18.log](https://pastebin.com/WVNXiFdA)
- [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
- [Software_4.18.log](https://pastebin.com/CwypQ4VF)
- [Security_4.18.log](https://pastebin.com/VV2ck2un)

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


** Tags: bot-comment
-- 
Ubuntu freezes after resume from suspend/hibernate in 10-15 sec
https://bugs.launchpad.net/bugs/1882917
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1768962] Re: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build

2020-06-10 Thread Colin Ian King
If this is still and issue please supply the DKMS make.log. If not, I'll
close this bug in 4 weeks.

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  nothing more to say -> failed to build in apt dist-upgrade...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-122-generic (x86_64)
   Do 3. Mai 21:43:07 CEST 2018
   make: *** Es wurden keine Ziele angegeben und keine „make“-Steuerdatei 
gefunden.  Schluss.
  DKMSKernelVersion: 4.4.0-122-generic
  Date: Thu May  3 21:43:11 2018
  InstallationDate: Installed on 2012-04-30 (2194 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageVersion: 0.6.5.6-0ubuntu21
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (699 days ago)

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

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


[Kernel-packages] [Bug 1764807] Re: [wishlist] please add zfsutils-linux to the seed(s)

2020-06-10 Thread Colin Ian King
The zfsutils package was added to the seed for the release Ubuntu 19.10
Eoan and is also supported in Focal and Groovy. This won't be supported
for older releases. Marking as fixed released.

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  [wishlist] please add zfsutils-linux to the seed(s)

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  For those using ZFS, it would sometimes be handy to have all the
  tooling available in the live environment. Currently, the live
  environment only has the kernel module which is unfortunately not
  enough to interact with this filesystem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu20
  ProcVersionSignature: Ubuntu 4.4.0-120.144-generic 4.4.117
  Uname: Linux 4.4.0-120-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 17 13:05:00 2018
  InstallationDate: Installed on 2016-12-06 (496 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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


[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake

2020-06-10 Thread Robie Basak
This is blocked on someone writing a test case as requested by Łukasz in
comment 10.

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

Title:
  Performance workaround for Dell 7390 2-in-1 Ice Lake

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  Incomplete

Bug description:
  == SRU justification focal ==

  As reported here:
  
https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 
5.4 kernel.
  The 5.4 kernel added support for "Processor thermal device", for Ice Lake, 
which will expose the power tables (via PPCC).

  This system default "max RAPL long term power limit" is 15W. But this
  power table is specifying as 9W. So thermald will limit power to 9W.

  If dptfxtract is executed, then power limit will be higher than power
  up value, but most of the users will use out of the box setup. So this
  need a workaround.

  This workaround will ignore any power limit less than the power up
  power limit.

  This is addressed in thermald 2.1 with two commits:
  
https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a
  
https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861

  I know 20.04 LTS uses 1.9.1. I can assist in backport if required.

  == Fix ==

  Two upstream commits to ease backporting:
     - eeadf7d2efe Restore to min state on deactivation without
   depending on hardware state
     - 9a6dc27879a Clean up the code and documentation

  Two upstream commits for the fix:
     - f7db4342933 Avoid polling power in non PPCC case
     - c3461690eaf Ignore invalid PPCC max power limit

  == Test case ==

  As reported here: https://www.phoronix.com/forums/forum/linux-
  graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-
  lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream

  == Regression Potential ==

  This fix involves changing the power limits logic so there is a potential 
that this may affect change the throttling behaviour of other systems with
  poorly defined PPCC power tables because it now ignores the power limits
  less than the power up limits. Users will see their machines run faster
  and hence active cooling may crank up (e.g. fans) but I think the speed
  improvement outweighs the noise factor.

  Note that these changes are already in thermald 2.1 that is now in
  Ubuntu  Groovy 20.10.

  ---

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

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


[Kernel-packages] [Bug 1882930] Re: focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10

2020-06-10 Thread Juerg Haefliger
** Also affects: linux-raspi (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  
  Upstream raspberrypi patchset 2020-06-10

 Ported from the following raspberrypi branch:
rpi-5.4.y

  from https://github.com/raspberrypi/linux.git

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

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


[Kernel-packages] [Bug 1882930] Re: focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10

2020-06-10 Thread Juerg Haefliger
** No longer affects: linux-raspi (Ubuntu Focal)

** Also affects: linux-raspi (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Focal:
  New

Bug description:
  
  Upstream raspberrypi patchset 2020-06-10

 Ported from the following raspberrypi branch:
rpi-5.4.y

  from https://github.com/raspberrypi/linux.git

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

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


[Kernel-packages] [Bug 1882945] [NEW] snd_hda_intel blocks/freezes suspend

2020-06-10 Thread Marcin
Public bug reported:

Since some packages upgrade(probalby couple months back; when I had LTS
bionic) I'm unable to suspend my PC.

I thought installing newest LTS focal will solve this problem but it
didn't - system freezes on suspend displaying plymouth last screen.

I found debug howto here :
https://www.kernel.org/doc/Documentation/power/s2ram.txt

What I found according to it:

lut 21 09:43:39 pc kernel: PM:   Magic number: 0:88:726
lut 21 09:43:39 pc kernel: PM:   hash matches drivers/base/power/main.c:1721
lut 21 09:43:39 pc kernel: block loop6: hash matches
lut 21 09:43:39 pc kernel: pci :01:00.1: hash matches
lut 21 09:43:39 pc kernel: rtc_cmos 00:06: setting system clock to 
2060-02-21T08:43:23 UTC (2844578603)

$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) 
I/O Memory Management Unit
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Kaveri P2P Bridge for 
GFX PCIe Port [1:0]
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller 
[AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 16)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller 
(rev 01)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 5
01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 
Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 06)
marcin@pc:/sys


$ ls /sys/devices/pci* 
:00:00.0  :00:02.1  :00:04.0  :00:11.0  :00:13.0  
:00:14.1  :00:14.4  :00:18.1  :00:18.4   pci_bus
:00:00.2  :00:03.0  :00:10.0  :00:12.0  :00:13.2  
:00:14.2  :00:14.5  :00:18.2  :00:18.5   power
:00:02.0  :00:03.1  :00:10.1  :00:12.2  :00:14.0  
:00:14.3  :00:18.0  :00:18.3  firmware_node  uevent


$ cat /sys/power/pm_trace_dev_match
resulted in: block and snd_hda_intel

as I was unable to force :
$ modprobe -r -f snd_hda_intel
modprobe: FATAL: Module snd_hda_intel is in use.

I did change /etc/default/grub to:
GRUB_CMDLINE_LINUX="snd_hda_intel.blacklist=1 modprobe.blacklist=snd_hda_intel"

then sudo grub-update.

After reboot suspend was finnaly working correctly 
but I've NO sound now:(


Googling on the internet I found:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/queue-5.0/alsa-hda-don-t-trigger-jackpoll_work-in-azx_resume.patch?id=ae96827ca4096488ee460a071834fe03022172d7

Is it possible that's the change that broke my suspend?

my board: Gigabyte GA-F2A88XM-DS2.

Can you fix this problem?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia

[Kernel-packages] [Bug 1881435] Re: System freeze

2020-06-10 Thread Nitro Kash
No. REISUB doesn't work. Mouse and keyboard doesn't work during the
freeze. I am not able to open a tty or ssh to the system. It is exactly
like what is described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961. But none
of the solutions worked for me, including removing xserver-xorg-video-
intel. I will try using the new 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/1881435

Title:
  System freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes randomly. Keyboard and mouse do not work at that time. I am 
not able to ssh to the computer or access tty. I am able to do only a hard 
reset. I tried some troubleshooting myself, but with my novice expertise with 
ubuntu. The freeze is more or less random. But it is possibly more frequent 
when running a video, like a youtube video in a browser. Freeze is more 
frequenty when going full screen with a video, a VM machine or a remote desktop 
through vnc4server.
  1. Tried removing some software like chrome, dropbox, virtualbox, etc. That 
did not help.
  2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 
kernel. That did not help either.
  3. Tried other distros like Mint and Fedora. Still had problem.
  4. Tried running with NVidia driver and xserver-xorg. The problem occured 
with both.
  5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured 
in both. 
  6. Tried all the suggestions in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were 
applicable. None of the suggestions helped.
  7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and 
experienced no crash/freeze with youtube running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 12:36:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651]
  InstallationDate: Installed on 2020-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: 

[Kernel-packages] [Bug 1797967] Re: zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build

2020-06-10 Thread Colin Ian King
Apologies for taking so long to get around to triage this issue. If this
is still an issue please attach the DKMS make.log file generated on the
failed build.

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

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I was doing an ordinary system update.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: zfs-dkms 0.7.5-1ubuntu16.4
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.7.5 for kernel 4.15.0-36-generic (x86_64)
   pon, 15 paź 2018, 21:35:50 CEST
   make: *** Nie podano obiektów i nie znaleziono makefile. Stop.
  DKMSKernelVersion: 4.15.0-36-generic
  Date: Mon Oct 15 21:35:50 2018
  InstallationDate: Installed on 2018-07-22 (85 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  PackageVersion: 0.7.5-1ubuntu16.4
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.7.5-1ubuntu16.4: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1882930] [NEW] focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10

2020-06-10 Thread Juerg Haefliger
Public bug reported:


Upstream raspberrypi patchset 2020-06-10

   Ported from the following raspberrypi branch:
  rpi-5.4.y

from https://github.com/raspberrypi/linux.git

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

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

Title:
  focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  
  Upstream raspberrypi patchset 2020-06-10

 Ported from the following raspberrypi branch:
rpi-5.4.y

  from https://github.com/raspberrypi/linux.git

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

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


[Kernel-packages] [Bug 1880213] Re: ext2 build failure on 4.4.0-180.210

2020-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-snapdragon - 4.4.0-1138.146

---
linux-snapdragon (4.4.0-1138.146) xenial; urgency=medium

  * xenial/linux-snapdragon: 4.4.0-1138.146 -proposed tracker (LP:
#1878869)

  * ext2 build failure on 4.4.0-180.210 (LP: #1880213)
- ext2: fix debug reference to ext2_xattr_cache

  [ Ubuntu: 4.4.0-180.210 ]

  * xenial/linux: 4.4.0-180.210 -proposed tracker (LP: #1878873)
  * Xenial update: 4.4.223 upstream stable release (LP: #1878232)
- mwifiex: fix PCIe register information for 8997 chipset
- drm/qxl: qxl_release use after free
- drm/qxl: qxl_release leak in qxl_draw_dirty_fb()
- staging: rtl8192u: Fix crash due to pointers being "confusing"
- usb: gadget: f_acm: Fix configfs attr name
- usb: gadged: pch_udc: get rid of redundant assignments
- usb: gadget: pch_udc: reorder spin_[un]lock to avoid deadlock
- usb: gadget: udc: core: don't starve DMA resources
- MIPS: Fix macro typo
- MIPS: ptrace: Drop cp0_tcstatus from regoffset_table[]
- MIPS: BMIPS: Fix PRID_IMP_BMIPS5000 masking for BMIPS5200
- MIPS: smp-cps: Stop printing EJTAG exceptions to UART
- MIPS: scall: Handle seccomp filters which redirect syscalls
- MIPS: BMIPS: BMIPS5000 has I cache filing from D cache
- MIPS: BMIPS: Clear MIPS_CACHE_ALIASES earlier
- MIPS: BMIPS: local_r4k___flush_cache_all needs to blast S-cache
- MIPS: BMIPS: Pretty print BMIPS5200 processor name
- MIPS: Fix HTW config on XPA kernel without LPA enabled
- MIPS: BMIPS: Adjust mips-hpt-frequency for BCM7435
- MIPS: math-emu: Fix BC1{EQ,NE}Z emulation
- MIPS: Fix BC1{EQ,NE}Z return offset calculation
- MIPS: perf: Fix I6400 event numbers
- MIPS: KVM: Fix translation of MFC0 ErrCtl
- MIPS: SMP: Update cpu_foreign_map on CPU disable
- MIPS: c-r4k: Fix protected_writeback_scache_line for EVA
- MIPS: Octeon: Off by one in octeon_irq_gpio_map()
- bpf, mips: fix off-by-one in ctx offset allocation
- MIPS: RM7000: Double locking bug in rm7k_tc_disable()
- MIPS: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO
- mips/panic: replace smp_send_stop() with kdump friendly version in panic
  path
- ARM: dts: armadillo800eva Correct extal1 frequency to 24 MHz
- ARM: imx: select SRC for i.MX7
- ARM: dts: kirkwood: gpio pin fixes for linkstation ls-wxl/wsxl
- ARM: dts: kirkwood: gpio pin fixes for linkstation ls-wvl/vl
- ARM: dts: kirkwood: gpio-leds fixes for linkstation ls-wxl/wsxl
- ARM: dts: kirkwood: gpio-leds fixes for linkstation ls-wvl/vl
- ARM: dts: orion5x: gpio pin fixes for linkstation lswtgl
- ARM: dts: orion5x: fix the missing mtd flash on linkstation lswtgl
- ARM: dts: kirkwood: use unique machine name for ds112
- ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile
- ARM: OMAP2+: hwmod: fix _idle() hwmod state sanity check sequence
- perf/x86: Fix filter_events() bug with event mappings
- x86/LDT: Print the real LDT base address
- x86/apic/uv: Silence a shift wrapping warning
- ALSA: fm801: explicitly free IRQ line
- ALSA: fm801: propagate TUNER_ONLY bit when autodetected
- ALSA: fm801: detect FM-only card earlier
- netfilter: nfnetlink: use original skbuff when acking batches
- xfrm: fix crash in XFRM_MSG_GETSA netlink handler
- mwifiex: fix IBSS data path issue.
- mwifiex: add missing check for PCIe8997 chipset
- iwlwifi: set max firmware version of 7265 to 17
- Bluetooth: btmrvl: fix hung task warning dump
- dccp: limit sk_filter trim to payload
- net/mlx4_core: Do not BUG_ON during reset when PCI is offline
- mlxsw: pci: Correctly determine if descriptor queue is full
- PCI: Supply CPU physical address (not bus address) to iomem_is_exclusive()
- alpha/PCI: Call iomem_is_exclusive() for IORESOURCE_MEM, but not
  IORESOURCE_IO
- vfio/pci: Allow VPD short read
- mlxsw: Treat local port 64 as valid
- IB/mlx4: Initialize hop_limit when creating address handle
- GRE: Disable segmentation offloads w/ CSUM and we are encapsulated via FOU
- powerpc/pci/of: Parse unassigned resources
- firmware: actually return NULL on failed request_firmware_nowait()
- c8sectpfe: Rework firmware loading mechanism
- net/mlx5: Avoid passing dma address 0 to firmware
- IB/mlx5: Fix RC transport send queue overhead computation
- net/mlx5: Make command timeout way shorter
- IB/mlx5: Fix FW version diaplay in sysfs
- net/mlx5e: Fix MLX5E_100BASE_T define
- net/mlx5: Fix the size of modify QP mailbox
- net/mlx5: Fix masking of reserved bits in XRCD number
- net/mlx5e: Fix blue flame quota logic
- net/mlx5: use mlx5_buf_alloc_node instead of mlx5_buf_alloc in
  mlx5_wq_ll_create
- net/mlx5: Avoid calling sleeping function by the health poll thread
- net/mlx5: Fix wait_vital for VFs and remove fixed sleep
- net/mlx5: Fix potential deadlock in 

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-06-10 Thread Rhonal Velasco
I was dealing with some of these issues after install new kernel version this 
morning. However I was able to boot with older kernel versions. After a lot of 
test, now I am able to boot in the new kernel without any problem.
Here there are some checks and tasks that I could accomplish:

-) Check in /etc/fstab and make sure that there are not duplicated mount
points for EFI.

-) Try apt install --reinstall linux-image-5.4.0-37-generic

-) Try sudo update-grub

Also, I removed drivers for nvidia and VirtualBox because some errors
that I saw in journalctl.

Hope this helps somebody.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions

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


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

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

apport-collect 1882944

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

Title:
  Resolution and settings changed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Resolution was set to 640x800 and not able to change it. Monitor and
  graphics drivers not recognized. All display settings changed and not
  correctable.

  Rebooted back to the 5.3 kernel and system is back to normal.

  May delete the 5.4 kernel until corrected.

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

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


[Kernel-packages] [Bug 1882917] Re: Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

2020-06-10 Thread AlekseyK
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Ubuntu freezes after resume from suspend/hibernate in 10-15 sec

Status in linux package in Ubuntu:
  New

Bug description:
  Asked her as well: https://askubuntu.com/questions/1247968/ubuntu-
  freezes-after-resume-from-suspend-hibernate-in-10-15-sec

  Bought new laptop - [Dell
  Latitude-5501][https://www.dell.com/ru/business/p/latitude-15-5501-laptop/pd]
  with Ubuntu 18.04.4. Works fine, however the only problem exists:
  after I close laptop cover or after some time of inactivity Ubuntu
  suspends or hibernate (do not know). After I resume it, it starts to
  work but in 10-15 sec Ubuntu freezes and I forced to power-off.

  Tried many things mentioned here:

  - blacklist nouveau
  - install older kernel - 4.14.41
  - update to newer - 4.18 or latest 5.3 kernel
  - switch to proprietary nvidia driver (was installed by default)
  - install `lightdm` instead of `gdm3`
  - dell software had run some recent firmware upgrade
  - etc

  Nothing work - it still freezes and it is impossible to work. The only
  suggestion I did not tried yet: install kubuntu and then original
  nvidia driver from manufacturer site. Do not know however if it
  affects warranty? ;) Any ideas how to solve, how to diagnose? Thanks!

  System, hardware and security logs during suspend/resume attached
  (original 4.15 kernel):

  - [System.log](https://pastebin.com/0Ttnu7T9)
  - [Security.log](https://pastebin.com/Wme1y1wM)
  - [Hardware.log](https://pastebin.com/ujUS5Ce4)

  Logs for 4.18 kernel are slightly different:

  - [System_4.18.log](https://pastebin.com/WVNXiFdA)
  - [Hardware_4.18.log](https://pastebin.com/RphtPj0w)
  - [Software_4.18.log](https://pastebin.com/CwypQ4VF)
  - [Security_4.18.log](https://pastebin.com/VV2ck2un)

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

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


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

2020-06-10 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  snd_hda_intel blocks/freezes suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since some packages upgrade(probalby couple months back; when I had
  LTS bionic) I'm unable to suspend my PC.

  I thought installing newest LTS focal will solve this problem but it
  didn't - system freezes on suspend displaying plymouth last screen.

  I found debug howto here :
  https://www.kernel.org/doc/Documentation/power/s2ram.txt

  What I found according to it:

  lut 21 09:43:39 pc kernel: PM:   Magic number: 0:88:726
  lut 21 09:43:39 pc kernel: PM:   hash matches drivers/base/power/main.c:1721
  lut 21 09:43:39 pc kernel: block loop6: hash matches
  lut 21 09:43:39 pc kernel: pci :01:00.1: hash matches
  lut 21 09:43:39 pc kernel: rtc_cmos 00:06: setting system clock to 
2060-02-21T08:43:23 UTC (2844578603)

  $ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Complex
  00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) 
I/O Memory Management Unit
  00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Kaveri P2P Bridge for 
GFX PCIe Port [1:0]
  00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
  00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA 
Controller [AHCI mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 
16)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (rev 01)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 0
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 1
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 2
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 3
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 4
  00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 5
  01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  marcin@pc:/sys

  
  $ ls /sys/devices/pci* 
  :00:00.0  :00:02.1  :00:04.0  :00:11.0  :00:13.0  
:00:14.1  :00:14.4  :00:18.1  :00:18.4   pci_bus
  :00:00.2  :00:03.0  :00:10.0  :00:12.0  :00:13.2  
:00:14.2  :00:14.5  :00:18.2  :00:18.5   power
  :00:02.0  :00:03.1  :00:10.1  :00:12.2  :00:14.0  
:00:14.3  :00:18.0  :00:18.3  firmware_node  uevent

  
  $ cat /sys/power/pm_trace_dev_match
  resulted in: block and snd_hda_intel

  as I was unable to force :
  $ modprobe -r -f snd_hda_intel
  modprobe: FATAL: Module snd_hda_intel is in use.

  I did change /etc/default/grub to:
  GRUB_CMDLINE_LINUX="snd_hda_intel.blacklist=1 
modprobe.blacklist=snd_hda_intel"

  then sudo grub-update.

  After reboot suspend was finnaly working correctly 
  but I've NO sound now:(

  
  Googling on the internet I found:
  

[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend

2020-06-10 Thread Glandos
Is there anything to add?

I saw also no answer from you on the LKML, do you want me to answer that
the patch is working for me? I'm not used to LKML, but I think I can try
:)

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

Title:
  Computer is frozen after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using an old HP EliteBook 6930p with current Ubuntu.

  When the computer is suspended, even after a fresh boot, it does not
  wake up: the power comes back, but the laptop is frozen, and does not
  respond to ping.

  It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

  I am holding kernel purge for now, but this is annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isabelle   1010 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 20:46:35 2020
  HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
  InstallationDate: Installed on 2015-03-15 (1830 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCU Ver. F.12
  dmi.board.name: 30DB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC939161W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 6930p
  dmi.product.sku: J1610781
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF

2020-06-10 Thread Junien Fridrick
Sorry for various reasons I won't be able to test 20.04

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

Title:
   mlx5 : not able to set a high MTU on the representor port for a VF

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25
  [1].

  With the distro driver, it's impossible to increase the MTU of a
  representor port :

  $ sudo ip li set enp50s0f0_0 mtu 1501
  RTNETLINK answers: Invalid argument

  Whereas with the OFED driver [2], I can set it up to 9978 :
  $ sudo ip li set mtu 9978 enp50s0f0_0
  $

  This is blocking to use OVS offloading with jumbo frames. Could we
  please get the feature in the distro driver ?

  Thanks !

  Steps to create the representor :

  echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs
  echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind
  sudo devlink dev eswitch set pci/:32:00.0 mode switchdev
  echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind

  [1] http://www.mellanox.com/related-docs/prod_adapter_cards
  /PB_ConnectX-5_VPI_Card_SocketDirect.pdf

  [2]
  
http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 11 14:18 seq
   crw-rw 1 root audio 116, 33 Apr 11 14:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr 11 14:42:57 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


[Kernel-packages] [Bug 1877858] Re: Improve TSC refinement (and calibration) reliability

2020-06-10 Thread Guilherme G. Piccoli
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Improve TSC refinement (and calibration) reliability

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  * We received a report recently of a missing TSC refinement across multiple 
reboots of a server, in an Intel Skylake-based processor. This was only 
reproducible in Bionic pre-5.0.

  * After checking kernel commits, we came up with 2 commits that
  largely improve the situation: a786ef152cdc ("x86/tsc: Make
  calibration refinement more robust")
  [git.kernel.org/linus/a786ef152cdc] and 604dc9170f24 ("x86/tsc: Use
  CPUID.0x16 to calculate missing crystal frequency")
  [git.kernel.org/linus/604dc9170f24]. We hereby request SRU for both of
  them.

  * The first commit contains improvement in comments and in an offset to match 
more recent (fast) machines, but the important part is a retry mechanism in the 
TSC refinement (in case it fails due to some disturbance on TSC read, like 
NMIs/SMIs).
   
  * The second commit is an improvement in TSC calibration for Skylake (and 
some other models), by checking a register instead of relying on table-based 
hardcoded values.

  * A note for Xenial (kernel 4.4): the second patch would require the
  inclusion of more commits, so given the "maturity" of this release
  (and the fact kernel 4.15 is an HWE for Xenial), I've kept it out of
  Xenial, backporting only the first and more important patch for 4.4 .

  [Test case]
  * Unfortunately there's not an easy way to test the effectiveness of the 
commits, specially the refinement improvement.

  * The user that reported us the missing refinements was able to test
  300 reboots with a regular Bionic kernel (and it reproduced the issue
  at least once), whereas when they tested with Bionic kernel + both
  hereby proposed commits, the problem didn't happen.

  * Regarding the calibration commit, it was well-tested by community
  using multiple machines and checking the TSC calibration read vs.
  tables present in instlatx64.atw.hu .

  [Regression potential]
  * We consider the regression potential low, specially due to the nature of 
the patches: the first is basically a retry mechanism (and some improvement in 
an offset to reflect more recent machines), and the 2nd is an improvement for 
TSC calibration on some platforms (that are currently hardcoded in a 
table-based way in kernel). Also, the patches are present upstream for a while 
and I couldn't find any fixes for them.

  * An hypothetical regression from the 2nd patch could be in TSC
  precision calculation, which refinement itself might as well
  circumvent. From the first patch, a bug in code is the one
  hypothetical regression I could think.

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

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


[Kernel-packages] [Bug 1826376] Re: cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers

2020-06-10 Thread Junien Fridrick
Sorry I won't be able to test 20.04 as I don't have a Chelsio NIC
anymore

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

Title:
  cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Using ubuntu 18.04 with kernel 4.15.0-47-generic, my Chelsio NIC can't
  offload VXLAN with the distro drivers (features "tx-udp_tnl-
  segmentation" and "tx-udp_tnl-csum-segmentation"), but with the OFED
  driver ("ChelsioUwire-3.10.0.0"), it can.

  Can we please get this in the distro driver ?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 19 14:48 seq
   crw-rw 1 root audio 116, 33 Apr 19 14:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr 25 08:53:20 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro Super Server
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=7b06790c-9447-446a-b1cf-b25104638b26 ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


[Kernel-packages] [Bug 1882936] [NEW] [Ubuntu 20.10] Secure Boot Testing for Ubuntu 20.10 with test kernel

2020-06-10 Thread bugproxy
Private bug reported:

x

** Affects: ubuntu-z-systems
 Importance: Undecided
 Status: New

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


** Tags: architecture-s39064 bugnameltc-186168 severity-high 
targetmilestone-inin2010

** Tags added: architecture-s39064 bugnameltc-186168 severity-high
targetmilestone-inin2010

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

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

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

Title:
  [Ubuntu 20.10] Secure Boot Testing for Ubuntu 20.10 with test kernel

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

Bug description:
  x

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

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


[Kernel-packages] [Bug 1881435] Re: System freeze

2020-06-10 Thread Kai-Heng Feng
Nothing suspicious from the log. Can magic key reboot the system?

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes randomly. Keyboard and mouse do not work at that time. I am 
not able to ssh to the computer or access tty. I am able to do only a hard 
reset. I tried some troubleshooting myself, but with my novice expertise with 
ubuntu. The freeze is more or less random. But it is possibly more frequent 
when running a video, like a youtube video in a browser. Freeze is more 
frequenty when going full screen with a video, a VM machine or a remote desktop 
through vnc4server.
  1. Tried removing some software like chrome, dropbox, virtualbox, etc. That 
did not help.
  2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 
kernel. That did not help either.
  3. Tried other distros like Mint and Fedora. Still had problem.
  4. Tried running with NVidia driver and xserver-xorg. The problem occured 
with both.
  5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured 
in both. 
  6. Tried all the suggestions in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were 
applicable. None of the suggestions helped.
  7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and 
experienced no crash/freeze with youtube running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 12:36:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651]
  InstallationDate: Installed on 2020-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1826869] Re: Can't mount High Speed SDXC Card

2020-06-10 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Can't mount High Speed SDXC Card

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I see the following error when I insert the SDXC Card (64GB High Speed
  - 170mbs)

  mmc1: error -110 whilst initialising SD card

  Same card works fine in under Windows and Chrome OS

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1551 F pulseaudio
   /dev/snd/pcmC0D0c:   rob1551 F...m pulseaudio
   /dev/snd/pcmC0D0p:   rob1551 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 21:31:55 2019
  InstallationDate: Installed on 2019-04-24 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Stream x360 Convertible 11-ag1XX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8501
  dmi.board.vendor: HP
  dmi.board.version: 05.21
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Stream x360 Convertible 11-ag1XX
  dmi.product.sku: 4RV86PA#ABG
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1882890] Re: Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

2020-06-10 Thread Andrea Gabellini
Hello,

same problem here!!!

which commands do you use to downgrade intel-microcode.

Thanks,
Andrea

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

Title:
  Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

Status in intel-microcode package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  This morning I applied the latest updates on my Ubuntu 16.04 (kernel
  4.15.0-106-generic + intel-microcode 3.20200609.0ubuntu0.16.04.0) and
  rebooted as usual to boot on the new kernel but the system won't boot:
  black screen.

  I tried booting the previous kernel 4.15.0-101 and it seems to be the
  same : in grub I select the 4.15.0-101 kernel, press enter, a message
  "Loading initrd..." is printed but nothing else happens.

  Tried even older kenrel 4.4.0-184-generic : same problem, "Loading
  initrd...", and nothing happens.

  I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-
  functionnal.

  I mounted the /boot partition from a USB rescue drive, and it seems that all 
the initrd images that got updated this morning are not bootable anymore :
  - initrd.img-4.15.0-106-generic
  - initrd.img-4.15.0.101-generic
  - initrd.img-4.4.0-184-generic

  I tried regenerating the images with update-initramfs but it's the
  same : "Loading initrd" message but nothing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890/+subscriptions

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


[Kernel-packages] [Bug 1875467] Re: Enable Invariant TSC Support

2020-06-10 Thread Stefan Bader
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-azure-4.15 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-azure (Ubuntu)
   Status: New => Invalid

** Changed in: linux-azure (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  Enable Invariant TSC Support

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Confirmed
Status in linux-azure source package in Eoan:
  Confirmed
Status in linux-azure-4.15 source package in Eoan:
  Invalid
Status in linux-azure source package in Focal:
  Confirmed
Status in linux-azure-4.15 source package in Focal:
  Invalid

Bug description:
  Microsoft would like to request two commits in all releases supported
  on Azure.  These commits benefit SAP workloads.

  These requested commits will enable support for Invariant TSC in Linux
  guest VMs.  The invariant TSC means that the TSC continues at a fixed
  rate regardless of the C-state or frequency of the processor (as long
  as the processor remains in the ACPI S0 state).

  These patches will allow guests to access the
  HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic
  MSR, which then enables the InvariantTSC feature.  After setting the
  synthetic MSR, CPUID will enumerate support for InvariantTSC.

  The following two commits enable support:
  9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/ 
InvariantTSC")
  dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")

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

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


[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

2020-06-10 Thread hugh chao
ok, let's wait until 5.4.0-38 in proposed and I will give it a try.

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  This is for alsa-ucm-conf:

  The patches are already in the mainline alsa-ucm-conf, so only
  sent the SRU for focal

  [Impact]
  On the machines without Intel HDMI, the sof driver will fail to initialize.

  [Fix]
  After fixing the kernel, we also need to change the ucm2 to make it
  support the machine without Intel hdmi audio.

  [Test Case]
  Boot the kernel on the machines without Intel HDMI audio, everything
  works well including the audio.

  [Regression Risk]
  Low, these 2 patches are already in the mainline alsa-ucm-conf. And we
  already tested them on 4 HP machines.

  
  This is for linux kernel:

  The patch is already in the oem-5.6 kernel and unstable kernel, so only
  sent the SRU for focal

  [Impact]
  On the machines without Intel HDMI, the sof driver will fail to initialize.

  [Fix]
  Intel upstream 2 patches in the kernel to fix it.

  [Test Case]
  Boot the kernel on the machines without Intel HDMI audio, everything
  works well including the audio.

  [Regression Risk]
  Low, these 2 patches are already in the mainline kernel.

  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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


[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-10 Thread Felix Flaherty
Same issues with JBL E50BT!!! :-/
Only the output is working (A2DP-Profil). But that's it no matter what changes 
I make to config's.

- Microphone is not working (no matter what profil is chosen)
- On A2DP listening to audio is possible

Ubuntu 20.04 - Linux 5.4.0-37-generic
pulseaudio 1:13.99.1-1ubuntu3.3 amd64
bluez 5.53-0ubuntu3 amd64

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Kernel-packages] [Bug 1818392] Re: kernel panic at boot time

2020-06-10 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  kernel panic at boot time

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Since several weeks there is a kernel panic after the upgrade to linux-image 
4.18.0-15-generic.
  Do you have an idea why it happened and when it will be fixed?
  Currently I have have to press several times the escape key when starting my 
laptop in order to select a working Linux kernel like 4.18.0-14-generic.

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

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


[Kernel-packages] [Bug 1882895] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.

2020-06-10 Thread Sophie
Fixed following this: https://askubuntu.com/questions/176121/dpkg-error-
trying-to-overwrite-file-which-is-also-in

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1010.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a bad one.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  squinton   1113 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 09:18:45 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-37.41_all.deb ...
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  DuplicateSignature:
   package:linux-tools-common:(not installed)
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1010.10
  InstallationDate: Installed on 2020-05-09 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 004: ID 05ac:024f Apple, Inc. 
   Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.9
  dmi.board.name: 0HD5W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool

2020-06-10 Thread Colin Ian King
The fix seems to be causing some issues, as reported here:

https://github.com/openzfs/zfs/pull/10331#issuecomment-636502835

..so I'm watching the upstream fixes to see how it all shakes out.

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   0:54.51 arc_prune 
  
  18472 root  20   00.0m   0.0m   0.0m R  53.6  0.0   2:08.73 arc_prune 
  
  29525 root  20   00.0m   0.0m   0.0m R  53.6  0.0   1:35.81 arc_prune 
  
  32291 root  20   00.0m   0.0m   0.0m S  53.6  0.0   1:28.00 

[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working

2020-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi - 5.4.0-1012.12

---
linux-raspi (5.4.0-1012.12) focal; urgency=medium

  * focal/linux-raspi: 5.4.0-1012.12 -proposed tracker (LP: #1878791)

  * Focal update: v5.4.36 upstream stable release (LP: #1876361)
- [Config] raspi: updateconfigs for ARM64_ERRATUM_1542419

  * Raspberry Pi 4B: USB OTG is not working (LP: #1861070)
- [Config] raspi: Set USB_DWC2_DUAL_ROLE=y

  * Missing v3d driver disables 3D support on RPi4 (LP: #1876862)
- [Config] raspi: Set DRM_V3D=m

  * focal/linux-raspi: Upstream raspberrypi patchset 2020-05-11 (LP: #1877928)
- SAUCE: media: bcm2835-unicam: Resync to upstream raspberrypi
- media: bcm2835-unicam: Add support for mulitple device nodes.
- media: bcm2835-unicam: Add embedded data node.
- media: bcm2835-unicam: Use dummy buffer if none have been queued
- media: bcm2835-unicam: Disable event-related ioctls on metadata node
- media: bcm2835-unicam: Add support for the FRAME_SYNC event
- media: imx219: Advertise embedded data node on media pad 1
- dts: bcm2711: EMMC2 can address the whole first GB
- driver: char: rpivid: Remove legacy name support
- driver: char: rpivid: Don't map more than wanted
- defconfig: Enable I2C_MUX_PINCTRL in all Pi configs
- dt: Implement an I2C pinctrl mux for BSC0.
- dtoverlays: Update CSI overlays to use i2c_csi_dsi
- dt: Update all mainline bcm283x dt files for i2c0 pinctrl mux
- ARM: dts: Create bcm2708-rpi-b-rev1.dts
- dts: bcm2711: set #size-cells = <2>
- dts: bcm2711: add "High Peripheral" mode overlay
- Revert "spi: spidev: Fix CS polarity if GPIO descriptors are used"
- spi: use_gpio_descriptor fixup moved to spi_setup
- overlays: rpivid-v4l2 also needs size-cells = 2
- media: bcm2835-unicam: Re-fetch mbus code from subdev on a g_fmt call
- uapi: bcm2835-isp: Add bcm2835-isp uapi header file
- media: uapi: v4l2-core: Add ISP statistics output V4L2 fourcc type
- media: uapi: v4l-ctrls: Add CID base for the bcm2835-isp driver
- staging: mmal-vchiq: Fix formatting errors in mmal_parameters.h
- staging: vc04_services: ISP: Add a more complex ISP processing component
- staging: vchiq: Load bcm2835_isp driver from vchiq
- configs: Add VIDEO_ISP_BCM2835 to all Pi defconfigs
- vc4_hvs: Mark core clock as optional
- vc4_hdmi: BCM2835 requires a fixed hsm clock for CEC to work
- configs: Enable CONFIG_DRM_VC4_HDMI_CEC
- media: i2c: imx219: Implement get_selection
- media: i2c: ov5647: Add support for g_selection to reflect 
cropping/binning
- media: i2c: ov5467: Fixup error path to release mutex
- media: i2c: ov5647: Support V4L2_CID_PIXEL_RATE
- media: i2c: ov5647: Set V4L2_SUBDEV_FL_HAS_EVENTS flag
- media: i2c: ov5647: Add support for V4L2_CID_VBLANK
- media: i2c: ov5647: Neither analogue gain nor exposure need 
EXECUTE_ON_WRITE
- media: i2c: ov5647: Use member names in mode tables
- media: i2c: ov5647: Advertise the correct exposure range
- media: i2c: imx219: Declare that the driver can create events
- media: bcm2835-unicam: Add support for VIDIOC_[S|G]_SELECTION
- media: bcm2835-unicam: Do not stop streaming in unicam_release
- media: bcm2835-unicam: Fix reference counting in unicam_open
- staging: vc04_services: ISP: Add enum_framesizes ioctl
- SQUASH: spi: Demote SPI_CS_HIGH warning to KERN_DEBUG
- ARM: dts: bcm2711: Allow 40-bit DMA for SPI
- overlays: Make the i2c-gpio overlay safe again
- staging: vc04_services: isp: Remove duplicated initialisation
- staging: vc04_services: isp: Make all references to bcm2835_isp_fmt const
- overlays: gpio-keys: Avoid open-drain warnings
- configs: Add missing PPS configs
- configs: Add missing TOUCHSCREEN_RASPBERRYPI_FW=m
- vc4_hdmi_phy: Fix typo in phy_get_cp_current
- overlays: Make use of intra-overlay fragments
- media: i2c: tc358743: Fix fallthrough warning
- media: bcm2835: unicam: Fix uninitialized warning
- video: bcm2708_fb: Disable FB if no displays found
- overlays: sc16is752-spi1: Add xtal parameter
- vc4_hdmi: Fix register offset when sending longer CEC messages
- vc4_hdmi: Fix up CEC registers
- vc4_hdmi_regs: Add Intr2 register block
- vc4_hdmi_regs: Make interrupt mask variant specific
- vc4_hdmi: Make irq shared
- vc4_hdmi: Adjust CEC ref clock based on its input clock
- vc4_hdmi: Remove cec_available flag as always supported
- config: Enable CONFIG_DRM_VC4_HDMI_CEC
- [Config] raspi: updateconfigs after update to rpi-5.4.y

  [ Ubuntu: 5.4.0-34.38 ]

  * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118)
  * debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
  * Focal update: v5.4.41 upstream stable release (LP: #1878649)
- USB: 

[Kernel-packages] [Bug 1882895] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common

2020-06-10 Thread Sophie
Public bug reported:

This seems to be a bad one.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
AptOrdering:
 linux-tools-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  squinton   1113 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Jun 10 09:18:45 2020
DpkgTerminalLog:
 Preparing to unpack .../linux-tools-common_5.4.0-37.41_all.deb ...
 Unpacking linux-tools-common (5.4.0-37.41) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
  trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
DuplicateSignature:
 package:linux-tools-common:(not installed)
 Unpacking linux-tools-common (5.4.0-37.41) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
  trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
InstallationDate: Installed on 2020-05-09 (31 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IwConfig:
 enp0s31f6  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 004: ID 05ac:024f Apple, Inc. 
 Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. OptiPlex 7040
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
RfKill:
 
SourcePackage: linux
Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.9
dmi.board.name: 0HD5W2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7040
dmi.product.sku: 06B9
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal package-conflict

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-oem-5.6-tools-common 5.6.0-1010.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a bad one.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  squinton   1113 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jun 10 09:18:45 2020
  DpkgTerminalLog:
   Preparing to unpack .../linux-tools-common_5.4.0-37.41_all.deb ...
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  DuplicateSignature:
   package:linux-tools-common:(not installed)
   Unpacking linux-tools-common (5.4.0-37.41) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-tools-common_5.4.0-37.41_all.deb (--unpack):
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-oem-5.6-tools-common 5.6.0-1010.10
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-oem-5.6-tools-common 5.6.0-1010.10
  InstallationDate: Installed on 2020-05-09 (31 days ago)
  

[Kernel-packages] [Bug 1882890] Re: Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

2020-06-10 Thread You-Sheng Yang
Hi, since you mentioned you also upgraded intel-microcode, does it help
if you regenerate initramfs after purging intel-microcode?

In addition, could you also paste your microcode info when booted with
USB rescue drive?

  $ dmesg |grep microcode:

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

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

** No longer affects: linux-hwe (Ubuntu)

** 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/1882890

Title:
  Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This morning I applied the latest updates on my Ubuntu 16.04 (kernel
  4.15.0-106-generic + intel-microcode 3.20200609.0ubuntu0.16.04.0) and
  rebooted as usual to boot on the new kernel but the system won't boot:
  black screen.

  I tried booting the previous kernel 4.15.0-101 and it seems to be the
  same : in grub I select the 4.15.0-101 kernel, press enter, a message
  "Loading initrd..." is printed but nothing else happens.

  Tried even older kenrel 4.4.0-184-generic : same problem, "Loading
  initrd...", and nothing happens.

  I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-
  functionnal.

  I mounted the /boot partition from a USB rescue drive, and it seems that all 
the initrd images that got updated this morning are not bootable anymore :
  - initrd.img-4.15.0-106-generic
  - initrd.img-4.15.0.101-generic
  - initrd.img-4.4.0-184-generic

  I tried regenerating the images with update-initramfs but it's the
  same : "Loading initrd" message but nothing happens.

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

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


[Kernel-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format

2020-06-10 Thread Alex Tu
$ udevadm info /dev/video0
P: /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/video4linux/video0
N: video0
L: 0
S: v4l/by-path/pci-:00:14.0-usb-0:5:1.0-video-index0
S: 
v4l/by-id/usb-CN09357GLOG0088EB05MX03_Integrated_Webcam_HD_200901010001-video-index0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/video4linux/video0
E: DEVNAME=/dev/video0
E: MAJOR=81
E: MINOR=0
E: SUBSYSTEM=video4linux
E: USEC_INITIALIZED=6424906
E: ID_V4L_VERSION=2
E: ID_V4L_PRODUCT=Integrated_Webcam_HD: Integrate
E: ID_V4L_CAPABILITIES=:capture:
E: ID_VENDOR=CN09357GLOG0088EB05MX03
E: ID_VENDOR_ENC=CN09357GLOG0088EB05MX03
E: ID_VENDOR_ID=0bda
E: ID_MODEL=Integrated_Webcam_HD
E: ID_MODEL_ENC=Integrated_Webcam_HD
E: ID_MODEL_ID=5672
E: ID_REVISION=8813
E: ID_SERIAL=CN09357GLOG0088EB05MX03_Integrated_Webcam_HD_200901010001
E: ID_SERIAL_SHORT=200901010001
E: ID_TYPE=video
E: ID_BUS=usb
E: ID_USB_INTERFACES=:0e0101:0e0201:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=uvcvideo
E: ID_PATH=pci-:00:14.0-usb-0:5:1.0
E: ID_PATH_TAG=pci-_00_14_0-usb-0_5_1_0
E: ID_FOR_SEAT=video4linux-pci-_00_14_0-usb-0_5_1_0
E: COLORD_DEVICE=1
E: COLORD_KIND=camera
E: DEVLINKS=/dev/v4l/by-path/pci-:00:14.0-usb-0:5:1.0-video-index0 
/dev/v4l/by-id/usb-CN09357GLOG0088EB05MX03_Integrated_Webcam_HD_200901010001-video-index0
E: TAGS=:snap_chromium_chromium:seat:uaccess:snap_chromium_chromedriver:


** Description changed:

  reproduce step:
-  - open cheese
-  - open preferences -> resolution
-  - only resolution from YUYV format in options
+  - open cheese
+  - open preferences -> resolution
+  - only resolution from YUYV format in options
+ 
+ the patches there works well and waiting for merge:
+ https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1build1
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:23:02 2020
  InstallationDate: Installed on 2020-04-12 (58 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  RelatedPackageVersions:
-  cheese3.34.0-1build1
-  cheese-common 3.34.0-1build1
+  cheese3.34.0-1build1
+  cheese-common 3.34.0-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

Title:
  cheese not recognize resolution in MJPG format

Status in Cheese:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  reproduce step:
   - open cheese
   - open preferences -> resolution
   - only resolution from YUYV format in options

  the patches there works well and waiting for merge:
  https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cheese 3.34.0-1build1
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  Uname: Linux 5.6.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 10 15:23:02 2020
  InstallationDate: Installed on 2020-04-12 (58 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Dell Inc. XPS 13 9380
  RelatedPackageVersions:
   cheese3.34.0-1build1
   cheese-common 3.34.0-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive

2020-06-10 Thread Raphael Raccuia
no "make" log I guess...
Tell me how I can compile any above version by sha, and I can reproduce.

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

Title:
  Esata port is dead after boot,  impossible to hotplug external drive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Esata doesn't work after boot: when hotplug an external drive, nothing 
happens, no dmesg or syslog.
  It works perfectly when booting on the external HDD itself, and it mounts 
after boot if plugging on grub prompt.
  Works on 4.15.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raphael1888 F pulseaudio
   /dev/snd/pcmC1D0p:   raphael1888 F...m pulseaudio
   /dev/snd/controlC0:  raphael1888 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de
  InstallationDate: Installed on 2018-03-17 (793 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: TOSHIBA TECRA A50-A
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-51-generic N/A
   linux-backports-modules-5.3.0-51-generic  N/A
   linux-firmware1.173.18
  Tags:  tara
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.10
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA A50-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: TECRA A50-A
  dmi.product.sku: PT641E
  dmi.product.version: PT641E-00600GS4
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1821305] Re: csiostor and cxgb4 fight for the NIC

2020-06-10 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  csiostor and cxgb4 fight for the NIC

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have a server with 2 * Chelsio T62100-LP-CR. Whenever the server is
  booted, the csiostor and cxgb4 modules will fight for the card.

  If csiostor wins, the following is logged :
  [9.331803] csiostor :21:00.6: PF: 6, Coming up as MASTER, HW state: 
Initializing
  ...
  [   15.048308] cxgb4 :21:00.4: Coming up as SLAVE: Adapter already 
initialized

  and then the interface comes up a 40 Gbps.

  If cxgb4 wins, however, the following is logged :
  [8.960020] cxgb4 :21:00.4: Coming up as MASTER: Initializing adapter
  ...
  [   12.141538] csiostor :21:00.6: PF: 6, Coming up as SLAVE, Master PF: 
4, HW state: Initialized

  and the interface comes up at 100 Gbps as expected.

  Since I'm not using FCoE, I blacklisted the csiostor module, but these
  2 modules should play nice with each other.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 15:42 seq
   crw-rw 1 root audio 116, 33 Mar 21 15:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Mar 22 09:05:38 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


  1   2   3   >