[Kernel-packages] [Bug 1848653] Re: package zfsutils-linux 0.8.1-1ubuntu14 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package zfsutils-linux 0.8.1-1ubuntu14 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Did an upgrade from 19.04 to 19.10. Eventually ran into the error:

  Errors were encountered while processing:
   zfsutils-linux
   zfs-zed
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Before I hit this error I had run into a failure in starting the
  service to mount ZFS filesystems due to an error about my mount point
  that uses ZFS not being empty. Not sure if this is relevant for the
  main issue though.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Thu Oct 17 23:26:25 2019
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-02-26 (963 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.1-1ubuntu14 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1848653/+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 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

[Khaled El Mously]

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

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

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

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

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

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+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 1850066] Re: [Star LabTop (Mk III)] Screen backlight pulses rapidly when cursor is still.

[Daniel van Vugt]

** No longer affects: mutter (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/1850066

Title:
  [Star LabTop (Mk III)] Screen backlight pulses rapidly when cursor is
  still.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The backlight for my display appears to brighten and dim rapidly
  whenever the mouse cursor is still, but stops when the cursor is being
  moved. The pulsing backlight is distracting and causes eye strain.
  Same issue experienced on Ubuntu 19.04 before upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 27 13:08:24 2019
  DistUpgraded: 2019-10-22 00:34:33,817 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation UHD Graphics 620 [8086:5917]
  InstallationDate: Installed on 2019-10-08 (19 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 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2085 Sunplus Innovation Technology Inc. HP HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs LabTop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=f6561506-cd05-4022-b582-c38a0a405d1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (5 days ago)
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0.09
  dmi.board.asset.tag: Default string
  dmi.board.name: Star LabTop (Mk III)
  dmi.board.vendor: Star Labs Online Limited
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0.09:bd07/05/2019:svnStarLabs:pnLabTop:pvrDefaultstring:rvnStarLabsOnlineLimited:rnStarLabTop(MkIII):rvrDefaultstring:cvnStarLabs:ct10:cvrDefaultstring:
  dmi.product.family: KBLR_NB_133
  dmi.product.name: LabTop
  dmi.product.sku: L3-U
  dmi.product.version: Default string
  dmi.sys.vendor: Star Labs
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fiona  1724 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-08 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Star Labs LabTop
  Package: mutter 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  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-19-generic 
root=UUID=f6561506-cd05-4022-b582-c38a0a405d1b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0.09
  

[Kernel-packages] [Bug 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[You-Sheng Yang]

** Also affects: ubuntux via
   https://bugzilla.kernel.org/show_bug.cgi?id=205123
   Importance: Unknown
   Status: Unknown

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in Gaming Edition:
  Unknown
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 | ADVANCED_SYSASSERT
  [   13.414976] iwlwifi :01:00.0: 0x | umac branchlink1
  [   13.414977] iwlwifi :01:00.0: 0xC008CC3C | umac branchlink2
  [   13.414978] iwlwifi :01:00.0: 0xC0087660 | umac interruptlink1
  

[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]

[You-Sheng Yang]

@otheos, could you help collect logs when the system becomes
unresponsive? You can paste the dmesg of the last boot after rebooting.

I cannot find same hw for test, so it would be on your own. You might
want to file a bug on https://bugzilla.kernel.org/ concurrently.

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

Title:
  iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem
  [8086:0010]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10
  Kernel 5.3.0-18-generic
  Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card.

  Expected: Wifi connects, uploads/downloads as normal

  Symptom: Wifi connects, as soon as an upload/download (any heavy
  traffic) start, the system comes to a crawl, becomes barely usable,
  and I end up opening a prompt to reboot.

  The system is unusable. This happens even with the Live USB version.

  The only solution I found was to download a different (newer) firmware.
  Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi

  This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz

  I then manually copy the contained firmware to /lib/firmware, remove
  all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode
  that the kernel expects to load.

  This completely resolves the issue.

  This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh 
installs):
  
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending 
SCAN_CFG_CMD: time out after 2000ms.
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue 
read_ptr 64 write_ptr 65
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting 
before reading
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, 
count: 609870115
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 
46.6bf1df06.0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | 
ADVANCED_SYSASSERT  
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | 
trm_hw_status0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | 
trm_hw_status1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | 
interruptlink1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | 
interruptlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode 
revision type
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode 
version major
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode 
version minor
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board 
version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | 
l2p_addr_match
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, 

[Kernel-packages] [Bug 1846214] Re: Freezes instead of suspending, most times

[Shahar Or]

Thank you for following up, Kai-Heng.

To answer your question, I don't remember ever having a reliable suspend
in this system.

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

Title:
  Freezes instead of suspending, most times

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi and thank you for all your free software work.

  This system usually freezes instead of suspending.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mightyiam   2139 F pulseaudio
   /dev/snd/controlC0:  mightyiam   2139 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 20:28:30 2019
  MachineType: Micro-Star International Co., Ltd. GS60 2QE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/ubuntu-encrypted_root_crypt ro splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-06-11 (112 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H5IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.111:bd02/22/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GS60 2QE
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+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 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

[Brendan]

Still panics. Looks like the same panic

** Attachment added: "20191028_230646.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+attachment/5301082/+files/20191028_230646.jpg

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

Title:
  Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error 
message stating 
  "Error: out of memory
  Press any key to continue..."

  After pressing a key, nothing changed. I left the room and came back
  to see that there was a kernel panic. I'll attach  picture as I
  couldn't copy/paste the console output.

  Description:  Ubuntu 19.10
  Release:  19.10

  linux-image-5.3.0-19-generic

  I expect the kernel to load without a panic.
  The kernel panicked.

  After rebooting and selecting an older kernel, I was able to boot and
  load the old kernel without issue (5.0.0-32-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lost   1947 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 28 00:52:26 2019
  HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626
  InstallationDate: Installed on 2016-06-17 (1227 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0WVDX2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5510
  dmi.product.sku: 06E5
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+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 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

[Brendan]

Using: linux-image-unsigned-5.4.0-050400rc5-generic

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

Title:
  Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error 
message stating 
  "Error: out of memory
  Press any key to continue..."

  After pressing a key, nothing changed. I left the room and came back
  to see that there was a kernel panic. I'll attach  picture as I
  couldn't copy/paste the console output.

  Description:  Ubuntu 19.10
  Release:  19.10

  linux-image-5.3.0-19-generic

  I expect the kernel to load without a panic.
  The kernel panicked.

  After rebooting and selecting an older kernel, I was able to boot and
  load the old kernel without issue (5.0.0-32-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lost   1947 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 28 00:52:26 2019
  HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626
  InstallationDate: Installed on 2016-06-17 (1227 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0WVDX2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5510
  dmi.product.sku: 06E5
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+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 1848953] Re: Intel wifi 3165 not working properly in Ubuntu 19.10

[You-Sheng Yang]

@florin two tests in need here:

[backport-iwlwifi-dkms]

1. Install backport-iwlwifi-dkms from PPA[1]:

  $ sudo add-apt-repository ppa:canonical-hwe-team/backport-iwlwifi && sudo 
apt-get update
  $ sudo apt-get install backport-iwlwifi-dkms

2. The installation step above should also trigger dkms module
installation for current kernel. You should make sure its status is
"installed" in the output of `dkms status`:

  $ dkms status
  backport-iwlwifi, 8042, 5.3.0-19-generic, x86_64: installed

3. Now reboot again and paste the dmesg log in /var/log/dmesg, not
screenshots.

[mainline kernel]

1. From Ubuntu mainline kernel page[2], scroll down to the end, find the
latest one, which should be v5.4-rc5. You'll need following ones:

  linux-headers-5.4.0-050400rc5_5.4.0-050400rc5.201910271430_all.deb
  linux-headers-5.4.0-050400rc5-generic_5.4.0-050400rc5.201910271430_amd64.deb
  
linux-image-unsigned-5.4.0-050400rc5-generic_5.4.0-050400rc5.201910271430_amd64.deb
  linux-modules-5.4.0-050400rc5-generic_5.4.0-050400rc5.201910271430_amd64.deb

which are basically arch-indep _all and arch-dependent -generic debs.
Download them and install with `dpkg -i *.deb`.

2. Reboot into the newly installed kernel. It should be the default
choice because it should be the newest kernel on your system, but you
might still need to interrupt grub and select the correct one.

3. Paste the dmesg log in /var/log/dmesg, not screenshots.

[1]: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/backport-iwlwifi
[2]: https://kernel.ubuntu.com/~kernel-ppa/mainline/

** Summary changed:

- Intel wifi 3165 not working properly in Ubuntu 19.10
+ Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in 
Ubuntu 19.10

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

Title:
  Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working
  properly in Ubuntu 19.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a clean install of the latest Ubuntu, 19.10, but since the live usb, a 
bug appeared.
  I could not login to the 2.4 GHz Wifi network at home with the fresh 
installed Ubuntu, it says the password is wrong, but it is not.

  I have Dual Band Intel AC 3165 it seems. My card appears in the
  Additional Drivers list with the notice that the device is not
  working. I can connect the 5 GHz wifi, but not the 2.4 GHz. See the
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florin 1194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 22:49:04 2019
  InstallationDate: Installed on 2019-10-19 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks TOSHIBA Web Camera - HD
   Bus 001 Device 006: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=0b07e060-55a5-4186-8670-bce4c230e596 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.sku: PSPUFE
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848953/+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 1846214] Re: Freezes instead of suspending, most times

[Kai-Heng Feng]

Unfortunately I don't see suspend attempt in the log.

Is this a regression?

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

Title:
  Freezes instead of suspending, most times

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi and thank you for all your free software work.

  This system usually freezes instead of suspending.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mightyiam   2139 F pulseaudio
   /dev/snd/controlC0:  mightyiam   2139 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 20:28:30 2019
  MachineType: Micro-Star International Co., Ltd. GS60 2QE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/ubuntu-encrypted_root_crypt ro splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-06-11 (112 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H5IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.111:bd02/22/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GS60 2QE
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+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 1850157] Re: nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed to build [error: void value not ignored as it ought to be]

[Daniel van Vugt]

It appears nvidia-graphics-drivers-418 does not exist in Ubuntu 19.10,
only 19.04. So this is just a result of upgrading.

Please just uninstall any nvidia v418 packages not in use.

** Summary changed:

- nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed to build
+ nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed to 
build [error: void value not ignored as it ought to be]

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed
  to build [error: void value not ignored as it ought to be]

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix

Bug description:
  Just upgraded to 19.10 and rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-kernel-source-418 (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 5.3.0-19-generic
  Date: Sat Oct 26 07:05:11 2019
  DuplicateSignature: 
dkms:nvidia-kernel-source-418:418.56-0ubuntu1:/var/lib/dkms/nvidia/418.56/build/common/inc/nv-linux.h:733:21:
 error: void value not ignored as it ought to be
  InstallationDate: Installed on 2019-08-08 (80 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageVersion: 418.56-0ubuntu1
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-418
  Title: nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed 
to build
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1850157/+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 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140

[David Ward]

** Package changed: alsa-driver (Ubuntu) => 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/1846539

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

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

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  irina   818 F pulseaudio
   /dev/snd/controlC0:  irina   818 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct  4 01:22:54 2019
  InstallationDate: Installed on 2019-02-12 (233 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  

[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (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/1846539

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

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

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  irina   818 F pulseaudio
   /dev/snd/controlC0:  irina   818 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct  4 01:22:54 2019
  InstallationDate: Installed on 2019-02-12 (233 days ago)
 

[Kernel-packages] [Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud

[gerald.yang]

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

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

Title:
  cloudimg: no iavf/i40evf module so no network available with SR-IOV
  enabled cloud

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in livecd-rootfs source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in livecd-rootfs source package in Eoan:
  New
Status in linux source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Invalid

Bug description:
  For example with bionic, i40evf module is in linux-modules-
  extra-4.15*-generic. However, cloudimg doesn't have linux-modules-
  extra seeded:

  $ curl -s 
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
 | grep linux-
  linux-base  4.5ubuntu1
  linux-headers-4.15.0-65 4.15.0-65.74
  linux-headers-4.15.0-65-generic 4.15.0-65.74
  linux-headers-generic   4.15.0.65.67
  linux-headers-virtual   4.15.0.65.67
  linux-image-4.15.0-65-generic   4.15.0-65.74
  linux-image-virtual 4.15.0.65.67
  linux-modules-4.15.0-65-generic 4.15.0-65.74
  linux-virtual   4.15.0.65.67

  We don't need the whole linux-modules-extra because the size is not
  small, but we need some VF drivers in cloud guest image embedded for
  SR-IOV enabled cloud including OpenStack. Otherwise, the guest is
  unusable with no network device.

  $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size
  Installed-Size: 171 MB

  $ du -h 
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko
  148K
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: livecd-rootfs (not installed)
  ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Thu Oct 17 10:48:41 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: livecd-rootfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1846214] Re: Freezes instead of suspending, most times

[Shahar Or]

Thank you for your assistance, Kai-Heng. Attached is the output of the
command you specified.

** Attachment added: "Output of `journalctl -b -1 -k`"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+attachment/5301075/+files/journalctl.log

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

Title:
  Freezes instead of suspending, most times

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi and thank you for all your free software work.

  This system usually freezes instead of suspending.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mightyiam   2139 F pulseaudio
   /dev/snd/controlC0:  mightyiam   2139 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 20:28:30 2019
  MachineType: Micro-Star International Co., Ltd. GS60 2QE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic 
root=/dev/mapper/ubuntu-encrypted_root_crypt ro splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-06-11 (112 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H5IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.111:bd02/22/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GS60 2QE
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+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 1850066] Re: [Star LabTop (Mk III)] Screen backlight pulses rapidly when cursor is still.

[Daniel van Vugt]

I wonder if the problem is related to panel self refresh, since it is
affected by hardware cursor movement.

Please try adding kernel parameter:

  i915.enable_psr=0

to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run:

  sudo update-grub

and reboot.

If that's the problem then it would make sense this bug is specific to
the model of LCD in this laptop.

https://www.kernel.org/doc/html/v5.3/gpu/i915.html#panel-self-refresh-psr-psr-srd
https://wiki.archlinux.org/index.php/intel_graphics#Screen_flickering

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

** Changed in: mutter (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/1850066

Title:
  [Star LabTop (Mk III)] Screen backlight pulses rapidly when cursor is
  still.

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The backlight for my display appears to brighten and dim rapidly
  whenever the mouse cursor is still, but stops when the cursor is being
  moved. The pulsing backlight is distracting and causes eye strain.
  Same issue experienced on Ubuntu 19.04 before upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 27 13:08:24 2019
  DistUpgraded: 2019-10-22 00:34:33,817 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation UHD Graphics 620 [8086:5917]
  InstallationDate: Installed on 2019-10-08 (19 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 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2085 Sunplus Innovation Technology Inc. HP HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs LabTop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=f6561506-cd05-4022-b582-c38a0a405d1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (5 days ago)
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0.09
  dmi.board.asset.tag: Default string
  dmi.board.name: Star LabTop (Mk III)
  dmi.board.vendor: Star Labs Online Limited
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0.09:bd07/05/2019:svnStarLabs:pnLabTop:pvrDefaultstring:rvnStarLabsOnlineLimited:rnStarLabTop(MkIII):rvrDefaultstring:cvnStarLabs:ct10:cvrDefaultstring:
  dmi.product.family: KBLR_NB_133
  dmi.product.name: LabTop
  dmi.product.sku: L3-U
  dmi.product.version: Default string
  dmi.sys.vendor: Star Labs
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fiona  1724 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-08 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Star Labs LabTop
  Package: mutter 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  

[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

[RyanNerd]

Here's a script that will get the wifi back up and running again without
a reboot:

```
#!/bin/sh

# If an interface name was not passed in then assume that wlo1 is the interface 
name.
if [ -z "$1" ]; then
interface="wlo1"
else
interface=$1
fi

# Figure out what pci slot Linux has assigned the Network controller: Intel 
Corporation Wireless 7260
wirelessPCI=$(lspci |grep "Wireless 7260")
pci=$(echo ${wirelessPCI} | awk '{ print $1 }')
devicePath="/sys/bus/pci/devices/:$pci/remove"

# Not the best solution as this script can hang. 
# But since if this script fails the ONLY way to revive the wifi anyway is a 
reboot...
# Feel free to improve the script if you have the scriptfu ninja skills to do 
so.
while true; do

# Tell Linux to remove the wifi card from the PCI device list only if it 
exists in the first place.
if [ -f $devicePath ]; then
echo 1 | sudo tee $devicePath > /dev/null
sleep 1
fi

# Reprobe the driver modules in case we have removed them in a failed 
attempt to wake the network card.
sudo modprobe iwlmvm
sudo modprobe iwlwifi

# Try to have Linux bring the network card back online as a PCI device. 
echo 1 | sudo tee /sys/bus/pci/rescan > /dev/null
sleep 1

# Check if Linux managed to bring the network card back online as a PCI 
device.
if [ -f $devicePath ]; then

# Looks like we are back in business. 
# So we try to set the PCI slot with some voodoo I don't understand 
that the Intel devs told me to try.
# https://bugzilla.kernel.org/show_bug.cgi?id=191601
sudo setpci -s $pci 0x50.B=0x40

# Bring the wireless network interface up.
sudo ifconfig $interface up

# Did the wifi interface actually go live?
exitCode=$?
if [ $exitCode -eq 0 ];then

# Not sure why in the hell this is not the default for wireless 
intefaces.
# It is well documented that: (power_management === ON) === 
Wifi-Stupidity
sudo iwconfig $interface power off

# The exit code will be the exit code of our attempt at turning 
power management off for $interface/wlan0.
break
fi
else
# It's worse than that the wifi's dead Jim! Dead Jim! Dead!
# We tell Linux to remove the the wifi driver modules and loop back in 
an attempt to revive the wifi.
sudo modprobe -r iwlmvm
sudo modprobe -r iwlwifi
fi
done

```

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

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error 

[Kernel-packages] [Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering

[Daniel van Vugt]

** Summary changed:

- [amdgpu] Mouse cursor movement is unequally
+ [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI 
stuttering

** Package changed: gnome-shell (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/1849917

Title:
  [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
  GUI stuttering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves 
unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 
19.10).
  For example: When I want to go to a button the cursor sometimes stops on the 
way to it and moves on milliseconds later.
  In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is 
not present.

  Please let me now if I can add some further information.

  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  All available system updates were installed. No extensions added
  additionally.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 06:23:01 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-20 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]

[Daniel van Vugt]

If you see changes like that after boot then please attach output from
'dmesg' showing the period of time when the change occurred.

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849917] [NEW] [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves 
unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 
19.10).
For example: When I want to go to a button the cursor sometimes stops on the 
way to it and moves on milliseconds later.
In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not 
present.

Please let me now if I can add some further information.

lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

All available system updates were installed. No extensions added
additionally.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 06:23:01 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-10-20 (5 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: 19.10 amd64 amdgpu apport-bug eoan performance regression-release
-- 
[iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI 
stuttering
https://bugs.launchpad.net/bugs/1849917
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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud

[Nobuto Murata]

** No longer affects: livecd-rootfs (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/1848481

Title:
  cloudimg: no iavf/i40evf module so no network available with SR-IOV
  enabled cloud

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in livecd-rootfs source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in livecd-rootfs source package in Eoan:
  New
Status in linux source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Invalid

Bug description:
  For example with bionic, i40evf module is in linux-modules-
  extra-4.15*-generic. However, cloudimg doesn't have linux-modules-
  extra seeded:

  $ curl -s 
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
 | grep linux-
  linux-base  4.5ubuntu1
  linux-headers-4.15.0-65 4.15.0-65.74
  linux-headers-4.15.0-65-generic 4.15.0-65.74
  linux-headers-generic   4.15.0.65.67
  linux-headers-virtual   4.15.0.65.67
  linux-image-4.15.0-65-generic   4.15.0-65.74
  linux-image-virtual 4.15.0.65.67
  linux-modules-4.15.0-65-generic 4.15.0-65.74
  linux-virtual   4.15.0.65.67

  We don't need the whole linux-modules-extra because the size is not
  small, but we need some VF drivers in cloud guest image embedded for
  SR-IOV enabled cloud including OpenStack. Otherwise, the guest is
  unusable with no network device.

  $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size
  Installed-Size: 171 MB

  $ du -h 
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko
  148K
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: livecd-rootfs (not installed)
  ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Thu Oct 17 10:48:41 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: livecd-rootfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud

[gerald.yang]

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: livecd-rootfs (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
   Status: Invalid

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
 Assignee: Nobuto Murata (nobuto)
   Status: Fix Committed

** Also affects: livecd-rootfs (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

Title:
  cloudimg: no iavf/i40evf module so no network available with SR-IOV
  enabled cloud

Status in linux package in Ubuntu:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in livecd-rootfs source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in livecd-rootfs source package in Eoan:
  New
Status in linux source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Invalid

Bug description:
  For example with bionic, i40evf module is in linux-modules-
  extra-4.15*-generic. However, cloudimg doesn't have linux-modules-
  extra seeded:

  $ curl -s 
http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest
 | grep linux-
  linux-base  4.5ubuntu1
  linux-headers-4.15.0-65 4.15.0-65.74
  linux-headers-4.15.0-65-generic 4.15.0-65.74
  linux-headers-generic   4.15.0.65.67
  linux-headers-virtual   4.15.0.65.67
  linux-image-4.15.0-65-generic   4.15.0-65.74
  linux-image-virtual 4.15.0.65.67
  linux-modules-4.15.0-65-generic 4.15.0-65.74
  linux-virtual   4.15.0.65.67

  We don't need the whole linux-modules-extra because the size is not
  small, but we need some VF drivers in cloud guest image embedded for
  SR-IOV enabled cloud including OpenStack. Otherwise, the guest is
  unusable with no network device.

  $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size
  Installed-Size: 171 MB

  $ du -h 
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko
  148K
/lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: livecd-rootfs (not installed)
  ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Thu Oct 17 10:48:41 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: livecd-rootfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1850238] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: disco

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.


  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit

  
  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
 +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 
Ti Mobile]
 |+-00.1  NVIDIA Corporation Device 1aeb
 |+-00.2  NVIDIA Corporation Device 1aec
 |\-00.3  NVIDIA Corporation Device 1aed
  ...

  Where the '1aed' device is detected as "NVIDIA USB Type-C Port Policy
  Controller" in Windows.

  I'm not sure if it's serving any useful purpose on this laptop, and it
  certainly doesn't seem to function properly:

  If I enable UCSI logging on startup (root's crontab):

  @reboot bash -c 'echo 1 >
  /sys/kernel/debug/tracing/events/ucsi/enable'

  ..the steps to reproduce above result in the following 
/sys/kernel/debug/tracing/trace:
  # tracer: nop
  #
  # 

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

[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/1850239

Title:
  Repeated Ubuntu internal errors. Greyed out WiFi

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Repeated notifications of internal errors in Ubuntu MATE 17.10. Lost
  WiFi connection and when I tried to reconnect, the WiFi menu item
  grayed out. Had to reboot to get WiFi back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2762 F pulseaudio
   /dev/snd/controlC0:  robert 2762 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Oct 28 21:23:37 2019
  InstallationDate: Installed on 2018-12-16 (316 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850239/+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 1850239] [NEW] Repeated Ubuntu internal errors. Greyed out WiFi

[Robert Pearson]

Public bug reported:

Repeated notifications of internal errors in Ubuntu MATE 17.10. Lost
WiFi connection and when I tried to reconnect, the WiFi menu item grayed
out. Had to reboot to get WiFi back.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-19-generic 5.3.0-19.20
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  robert 2762 F pulseaudio
 /dev/snd/controlC0:  robert 2762 F pulseaudio
CurrentDesktop: MATE
Date: Mon Oct 28 21:23:37 2019
InstallationDate: Installed on 2018-12-16 (316 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-generic N/A
 linux-backports-modules-5.3.0-19-generic  N/A
 linux-firmware1.183.1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A
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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug eoan

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

Title:
  Repeated Ubuntu internal errors. Greyed out WiFi

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Repeated notifications of internal errors in Ubuntu MATE 17.10. Lost
  WiFi connection and when I tried to reconnect, the WiFi menu item
  grayed out. Had to reboot to get WiFi back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2762 F pulseaudio
   /dev/snd/controlC0:  robert 2762 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Oct 28 21:23:37 2019
  InstallationDate: Installed on 2018-12-16 (316 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850239/+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 1850238] [NEW] ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

[Nickolay Ponomarev]

Public bug reported:

Short version
=
I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

It happens with the newer kernel (5.3 series; I'm currently running the
version from eoan-proposed), but not with the version from the Ubuntu
18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu SMP").

[I haven't yet tried to test the mainline builds, nor to find/confirm
the regression range, as this seems like something that will take me
another week, and I'm not sure if it would be helpful.]

I narrowed the problem down to what I believe is a broken USB Type-C
controller on the NVIDIA GPU: the ucsi_ccg driver for
/sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports a
timeout for both the initial PPM_RESET command (on system startup) and
for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

I guess the hang is the driver waiting for a response to
SET_NOTIFICATION_ENABLE; it appears to have been added recently in
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
which could explain why I don't see the hang with 5.0.x.

Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line (and
rebooting) makes the hang go away.


Steps to reproduce
==
(these are not the actual steps one can take to reproduce, starting from a new 
install; let me know if those will be useful)

1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
# (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
# guessed it's better to avoid it, 
and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

2. Run `dmesg -w` and wait a minute or two until a message like the
following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

(attempting to suspend before the PPM init timeout will fail to enter sleep at 
all.)
(if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

3. Run `sudo pm-suspend` (using the power button to suspend causes other
problems)

...wait for the laptop to go to sleep and the fans to turn off.

4. Press Enter on the built-in keyboard to resume. (Although the way we
wake up the system doesn't seem to matter.)

5. Observe a hang lasting for almost a minute before the system is
operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit


System info
===

My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read future 
VR headsets are supposed to use it 
),
 and indeed I'm seeing:

# lspci -tv
-[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
   +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 Ti 
Mobile]
   |+-00.1  NVIDIA Corporation Device 1aeb
   |+-00.2  NVIDIA Corporation Device 1aec
   |\-00.3  NVIDIA Corporation Device 1aed
...

Where the '1aed' device is detected as "NVIDIA USB Type-C Port Policy
Controller" in Windows.

I'm not sure if it's serving any useful purpose on this laptop, and it
certainly doesn't seem to function properly:

If I enable UCSI logging on startup (root's crontab):

@reboot bash -c 'echo 1 >
/sys/kernel/debug/tracing/events/ucsi/enable'

..the steps to reproduce above result in the following 
/sys/kernel/debug/tracing/trace:
# tracer: nop
#
# entries-in-buffer/entries-written: 10/10   #P:12
#
#  _-=> irqs-off
# / _=> need-resched
#| / _---=> hardirq/softirq
#|| / _--=> preempt-depth
#||| / delay
#   TASK-PID   CPU#  TIMESTAMP  FUNCTION
#  | |   |      | |
 kworker/6:2-679   [006] 68.593915: ucsi_command: control=0001 
(PPM_RESET)
 kworker/6:1-187   [006]    151.599387: 

[Kernel-packages] [Bug 1846335] Re: [CML] New device id's for CMP-H

[quanxian]

** Description changed:

  split from bug 1843774
  
  Description
  This task is to identify what new device IDs are required for CML PCH-H.
  
  Controller Kernel Version Commit Approved to be published Comments
  USB device/xDCI 0x02ee v5.2 7ae622c978db6b2
  I²C (CMP-H)|0x06c5 0x06c6 0x06e8 0x06e9 0x06ea 0x06eb
  HS-UART (CMP-H) 0x06a8 0x06a9 0x06c7
  SPI (CMP-H) 0x06aa 0x06ab 0x06fb
  
  SPI Flash Controller (CMP-H) 0x06a4 https://lore.kernel.org/linux-
  mtd/20191023145140.51427-1-mika.westerb...@linux.intel.com/
  
- GPIO (CMP-H) ???
+ GPIO(CMP-H) INT3450 "It seems the same as for CNL, nothing needs to be done 
here.
  SD Card (CMP-H) 0x06f5 v5.4-rc1 8f05eee67c1404a
  SMBus (CMP-H) 0x06a3 v5.5 07f047e3fe33
  
  Target Release: 19.10

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

Title:
  [CML] New device id's for CMP-H

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New

Bug description:
  split from bug 1843774

  Description
  This task is to identify what new device IDs are required for CML PCH-H.

  Controller Kernel Version Commit Approved to be published Comments
  USB device/xDCI 0x02ee v5.2 7ae622c978db6b2
  I²C (CMP-H)|0x06c5 0x06c6 0x06e8 0x06e9 0x06ea 0x06eb
  HS-UART (CMP-H) 0x06a8 0x06a9 0x06c7
  SPI (CMP-H) 0x06aa 0x06ab 0x06fb

  SPI Flash Controller (CMP-H) 0x06a4 https://lore.kernel.org/linux-
  mtd/20191023145140.51427-1-mika.westerb...@linux.intel.com/

  GPIO(CMP-H) INT3450 "It seems the same as for CNL, nothing needs to be done 
here.
  SD Card (CMP-H) 0x06f5 v5.4-rc1 8f05eee67c1404a
  SMBus (CMP-H) 0x06a3 v5.5 07f047e3fe33

  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1846335/+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 1850229] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1850229

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

Title:
  [CML-U] new network device support- e1000e: Add support for Comet
  Lake:

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

Bug description:
  Description:
  e1000e: network support for CML

  
  This patch on intel-wired-lan enables CML support: [v1] e1000e: Add support 
for Comet Lake: https://patchwork.ozlabs.org/patch/1174394/. It is not on 
net-next yet. 

  Keep tune until it is in upstream.

  target kernel: 5.4
  target release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1850229/+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 1850229] [NEW] [CML-U] new network device support- e1000e: Add support for Comet Lake:

[quanxian]

Public bug reported:

Description:
e1000e: network support for CML


This patch on intel-wired-lan enables CML support: [v1] e1000e: Add support for 
Comet Lake: https://patchwork.ozlabs.org/patch/1174394/. It is not on net-next 
yet. 

Keep tune until it is in upstream.

target kernel: 5.4
target release: 20.04

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-20.04

** Also 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/1850229

Title:
  [CML-U] new network device support- e1000e: Add support for Comet
  Lake:

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

Bug description:
  Description:
  e1000e: network support for CML

  
  This patch on intel-wired-lan enables CML support: [v1] e1000e: Add support 
for Comet Lake: https://patchwork.ozlabs.org/patch/1174394/. It is not on 
net-next yet. 

  Keep tune until it is in upstream.

  target kernel: 5.4
  target release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1850229/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849852, bug 1849005
-   bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
+   bionic/linux/pc-lowlatency-kernel: bug 1849853, bug 1849006
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849852, bug 1849005
bionic/linux/pc-lowlatency-kernel: bug 1849853, bug 1849006
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850117] Re: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch

[dann frazier]

** Changed in: kunpeng920/ubuntu-20.04
Milestone: None => ubuntu-20.04-ga

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

Title:
  [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-19.10 series:
  Triaged
Status in kunpeng920 ubuntu-20.04 series:
  Triaged
Status in kunpeng920 upstream-kernel series:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Bug Description]
   hpre patchset have merged into mainline 5.4rc3 kernel. Can use this hpre 
patchset to release UOSE basing this ubuntu 18.04.4 kernel branch, then merge 
into ubuntu 18.04.4 version.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

   crypto: hisilicon - add HiSilicon HPRE accelerator
crypto: hisilicon - add SRIOV support for HPRE
Documentation: Add debugfs doc for hisi_hpre
crypto: hisilicon: Add debugfs for HPRE
MAINTAINERS: Add maintainer for HiSilicon HPRE driver

  https://www.mail-archive.com/linux-
  cry...@vger.kernel.org/msg40969.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1850117/+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 1850117] Re: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch

[dann frazier]

** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.5

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

Title:
  [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-19.10 series:
  Triaged
Status in kunpeng920 ubuntu-20.04 series:
  Triaged
Status in kunpeng920 upstream-kernel series:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Bug Description]
   hpre patchset have merged into mainline 5.4rc3 kernel. Can use this hpre 
patchset to release UOSE basing this ubuntu 18.04.4 kernel branch, then merge 
into ubuntu 18.04.4 version.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

   crypto: hisilicon - add HiSilicon HPRE accelerator
crypto: hisilicon - add SRIOV support for HPRE
Documentation: Add debugfs doc for hisi_hpre
crypto: hisilicon: Add debugfs for HPRE
MAINTAINERS: Add maintainer for HiSilicon HPRE driver

  https://www.mail-archive.com/linux-
  cry...@vger.kernel.org/msg40969.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1850117/+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 1850117] Re: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch

[dann frazier]

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: kunpeng920/upstream-kernel
   Status: New => Triaged

** Also affects: kunpeng920/ubuntu-20.04
   Importance: Undecided
   Status: New

** Changed in: kunpeng920/ubuntu-20.04
   Status: New => Triaged

** Changed in: kunpeng920/ubuntu-19.10
   Status: New => Triaged

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: New => Triaged

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

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

** Changed in: kunpeng920
   Status: New => Triaged

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

Title:
  [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-19.10 series:
  Triaged
Status in kunpeng920 ubuntu-20.04 series:
  Triaged
Status in kunpeng920 upstream-kernel series:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Eoan:
  Triaged
Status in linux source package in Focal:
  Triaged

Bug description:
  [Bug Description]
   hpre patchset have merged into mainline 5.4rc3 kernel. Can use this hpre 
patchset to release UOSE basing this ubuntu 18.04.4 kernel branch, then merge 
into ubuntu 18.04.4 version.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

   crypto: hisilicon - add HiSilicon HPRE accelerator
crypto: hisilicon - add SRIOV support for HPRE
Documentation: Add debugfs doc for hisi_hpre
crypto: hisilicon: Add debugfs for HPRE
MAINTAINERS: Add maintainer for HiSilicon HPRE driver

  https://www.mail-archive.com/linux-
  cry...@vger.kernel.org/msg40969.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1850117/+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 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Ari]

For reference, here is the output, but with an old intel wifi card 7260
that works perfectly well and is installed in the same X16 PCIE slot
where the AX200 fails to load its firmware.

The AX200 was supposed to replace the 7260 however due to this problem
I've had to roll back the upgrade.

https://paste.ubuntu.com/p/FywHwCJYq5/

FWIW the system CPU is kabylake core i7, with a z170 chipset

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 | 

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

[Ubuntu Kernel Bot]

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

apport-collect 1850117

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

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

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

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

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

Title:
  [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  New
Status in kunpeng920 ubuntu-18.04-hwe series:
  New
Status in kunpeng920 ubuntu-19.10 series:
  New
Status in kunpeng920 upstream-kernel series:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Bug Description]
   hpre patchset have merged into mainline 5.4rc3 kernel. Can use this hpre 
patchset to release UOSE basing this ubuntu 18.04.4 kernel branch, then merge 
into ubuntu 18.04.4 version.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

   crypto: hisilicon - add HiSilicon HPRE accelerator
crypto: hisilicon - add SRIOV support for HPRE
Documentation: Add debugfs doc for hisi_hpre
crypto: hisilicon: Add debugfs for HPRE
MAINTAINERS: Add maintainer for HiSilicon HPRE driver

  https://www.mail-archive.com/linux-
  cry...@vger.kernel.org/msg40969.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1850117/+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 1850117] Re: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch

[dann frazier]

This appears to be a new driver, so backporting it should not be a
significant regression risk.

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

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

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

Title:
  [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  New
Status in kunpeng920 ubuntu-18.04-hwe series:
  New
Status in kunpeng920 ubuntu-19.10 series:
  New
Status in kunpeng920 upstream-kernel series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  New

Bug description:
  [Bug Description]
   hpre patchset have merged into mainline 5.4rc3 kernel. Can use this hpre 
patchset to release UOSE basing this ubuntu 18.04.4 kernel branch, then merge 
into ubuntu 18.04.4 version.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

   crypto: hisilicon - add HiSilicon HPRE accelerator
crypto: hisilicon - add SRIOV support for HPRE
Documentation: Add debugfs doc for hisi_hpre
crypto: hisilicon: Add debugfs for HPRE
MAINTAINERS: Add maintainer for HiSilicon HPRE driver

  https://www.mail-archive.com/linux-
  cry...@vger.kernel.org/msg40969.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1850117/+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 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error

[Manoj Iyer]

IBM,

Please test the Bionic *and* Disco kernels available in PPA:
https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1848127

Post the test output from *both* the kernels to this report. Once I get
positive test results I can SRU the patches.

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

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

** Changed in: ubuntu-power-systems
   Status: In Progress => Incomplete

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Manoj Iyer (manjo)

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Manoj Iyer (manjo)

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

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

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

Title:
  [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check
  Error

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Disco:
  Incomplete
Status in linux source package in Eoan:
  In Progress

Bug description:
  [IMPACT]
  MCE test renders the system unresponsive on P9 open power hardware 
(Withersoon)

  [TEST]
  A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see 
the [OTHER] section for test details and comment #7 for results with the PPA 
kernel. 

  [FIX]
  IBM has identified the following patch that fixes this issue:
  commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee
  Author: Balbir Singh 
  Date:   Tue Aug 20 13:43:47 2019 +0530

  powerpc/mce: Fix MCE handling for huge pages

  [REGRESSION POTENTIAL]
  The patch is applicable the powerpc architecture and limited in scope to MCE 
handling for huge pages. Patch does not touch any generic code. Regression if 
any is limited to powerpc MCE handling.

  [OTHER]
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-05-07 
23:31:20 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images built  
from the upstream op-build git tree.

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
   open-power-witherspoon-v2.3-rc2-58-g59fd0743
  buildroot-2019.02.2-17-g93b841d204
  skiboot-v6.3-rc2
  hostboot-19a436e
  occ-58e422d
  linux-5.0.9-openpower1-p3a4d5a4
  petitboot-v1.10.3
  machine-xml-a6f4df3
  hostboot-binaries-hw043019a.940
  capp-ucode-p9-dd2-v4
  sbe-249671d
  hcode-hw040319a.940

  Then enable sw xstop manually by using below command:

  root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable
  root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config
  "ibm,skiboot" Partition
  --
  experimental-fast-reset=1
  snarf-mode=noo
  opal-sw-xstop=enable

  Then from the Linux HOST injected the MCE UE Error on the machine as
  follows:

  root@ltc-wspoon11:~# ./probe_cpus.sh -L
  CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs:  0 1 2 3
  CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs:  4 5 6 7
  CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs:  8 9 10 11
  CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs:  12 13 14 15
  CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs:  16 17 18 19
  CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs:  20 21 22 23
  CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs:  24 25 26 27
  CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs:  28 29 30 31
  CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs:  32 33 34 35
  CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs:  36 37 38 39
  CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs:  40 41 42 43
  CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs:  44 45 46 47
  CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs:  48 49 50 51
  CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs:  52 53 54 55
  CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs:  56 57 58 59
  CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs:  60 61 62 63
  CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs:  64 65 66 67
  CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs:  68 69 70 71
  CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs:  72 73 74 75
  CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs:  76 77 78 79
  CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs:  80 81 82 83
  CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs:  84 85 86 87
  CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs:  88 89 90 91
  CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs:  92 93 94 95
  CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs:  96 97 98 99
  CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs:  100 101 102 103
  CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs:  104 105 106 107

[Kernel-packages] [Bug 1849641] Re: New upstream release: bluez 5.51

[Sebastien Bacher]

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  New upstream release: bluez 5.51

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  New upstream release: bluez 5.51

  http://www.bluez.org/release-of-bluez-5-51/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849641/+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 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)

[Arek Plich]

I have the same computer model (huawei matebook d 14 "ryzen 2500 and
vega graphics) and also under kubuntu 19.10 I have a problem with
artifacts on the screen (both in firefox and e.g. application for
watching popcorn time movies).

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

Title:
  [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
  2500u (Raven Ridge)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous window 
appear in the newly opened window.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-08 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+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 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848984
  packages:
lrm: linux-restricted-modules-aws-5.0
main: linux-aws-5.0
meta: linux-meta-aws-5.0
  phase: Testing
  phase-changed: Wednesday, 23. October 2019 16:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1848984
  packages:
lrm: linux-restricted-modules-aws-5.0
main: linux-aws-5.0
meta: linux-meta-aws-5.0
  phase: Testing
  phase-changed: Wednesday, 23. October 2019 16:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848983/+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 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140

[David Ward]

Ubuntu kernel team:

In the kernel package for Ubuntu, CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL
(introduced in 5.2-rc1) needs to be changed from 'Y' back to its default
value of 'N'. As described by Intel, this option cannot currently be set
together with CONFIG_SND_SOC_INTEL_SST_TOPLEVEL.

** 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/1846539

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   

[Kernel-packages] [Bug 1752829]

[Yassine]

Why is the core clock for this GPU (HAINAN) and what seems to have
codename OLAND hard-coded anyway? The other GPUs do not have their
clocks hard-coded, which allows them to be modified without modifying
and rebuilding the module.

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

Title:
  AMD HAINAN (Radeon R5 M330) Clock frequency is 750MHz while it is
  supposed to be 1030MHz

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

Bug description:
  Kernel source: /drivers/gpu/drm/radeon/si_dpm.c line 2985:

  max_sclk = 75000;

  instead of

  max_sclk = 103000;

  Why is that? I changed it and rebuilt the kernel, and I can say that
  there are absolutely no issues when using the 1030MHz clock, which is
  what it is supposed to be.

  Linux Version: 4.13.0-36-generic

  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yassine3068 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=e9860ff6-0207-40ae-b2dd-115d7c7956b8
  InstallationDate: Installed on 2016-12-19 (439 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57d6 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 25a7:0701  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=070ac60f-63d1-48e3-9322-44812d365c40 ro quiet splash radeon.runpm=1 
vt.handoff=7 initrd=boot\initrd.img-4.13.0-36-generic
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (135 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/24/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.34
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1D:bd11/24/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1752829/+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 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work

[Donatas]

Uninstalled the previous kernel, installed this one and did a full
power-off/power-on - touchscreen is still not working.

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

Title:
  Raydium Touchscreen on ThinkPad L390 does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on 
Windows, but not on Ubuntu.
  I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and 
running Live USB image, and also other distributions (Manjaro i3, Kubuntu).
  There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: 
https://certification.ubuntu.com/hardware/201812-26720

  Other info:
  - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer 
(2)]"
  - if I list device props using `xinput list-props 10`, I see device: `Device 
Node (277): "/dev/input/event9"`
  - `cat /dev/input/event9` does not produce anything
  - `xinput --test-xi2 --root` does not produce any touchscreen events, even 
though events from other devices are successfully shown

  Also, attached `ubuntu-bug` report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1821 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 18:32:07 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NRCTO1WW
  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.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R10ET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NRCTO1WW
  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:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NRCTO1WW:pvrThinkPadL390:rvnLENOVO:rn20NRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L390
  dmi.product.name: 20NRCTO1WW
  dmi.product.sku: LENOVO_MT_20NR_BU_Think_FM_ThinkPad L390
  dmi.product.version: ThinkPad L390
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721/+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 1850195] [NEW] Update EFA driver to 1.4.1

[Connor Kuehl]

Public bug reported:

Version 1.4.1 of the EFA driver has been tagged: https://github.com/amzn
/amzn-drivers/releases/tag/efa_linux_1.4.1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-aws (Ubuntu Eoan)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

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

** Changed in: linux-aws (Ubuntu Bionic)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

** Changed in: linux-aws (Ubuntu Disco)
 Assignee: (unassigned) => Connor Kuehl (connork)

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

Title:
  Update EFA driver to 1.4.1

Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-aws source package in Disco:
  In Progress
Status in linux-aws source package in Eoan:
  In Progress

Bug description:
  Version 1.4.1 of the EFA driver has been tagged:
  https://github.com/amzn/amzn-drivers/releases/tag/efa_linux_1.4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1850195/+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 1844384] Re: Display bug with kernel 5.2/5.3 on Dell XPS 13

[Dani]

I have the same XPS 13 model and I can confirm this, happened to me when
I updated Ubuntu to 19.04 to 19.10 (went from 5.0 to 5.2 i think) and I
started to have worst visual glitches. My screen freezes  (not my system
because if i have a secondary display works fine) with heavy and a
distorted image. I switched to Manjaro to try if the issues continued
and they did, same as i had with Ubuntu. I can attach screenshots lates
if someone is interested. Im willing to help with anything you guys
want.

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

Title:
  Display bug with kernel 5.2/5.3 on Dell XPS 13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I use in multiboot Ubuntu and Archlinux, I had the opportunity to use
  many kernels and I notice a random display problem (see screenshot)
  that happens from time to time on my Dell XPS but only from kernel 5.2
  (and following).

  Under Ubuntu 19.04 with the 5.0 kernel I don't have this problem,
  under Archlinux with the old kernels (4.19LTS, 5.0, 5.1) I didn't have
  this problem either.

  But since 5.2 whether it is under Ubuntu or Archlinux, I have noticed
  this problem which is difficult to describe, it is a kind of band that
  appears at the top of the screen with a different size (sometimes very
  wide).

  The problem occurs randomly, sometimes it can go 30 minutes without
  seeing it appear and sometimes it can appear full of times for a few
  minutes.

  The problem is not specific to Ubuntu but to the kernel since 5.2 and 
following. 
  Under the 19.10 of Ubuntu in development with the 5.3 kernel, the problem is 
still present.

  Could you please forward this bug to the team that deals with the linux 
kernel.
  (the 2 screenshots were taken under Ubuntu 19.10 with the 5.3 kernel but 
under Archlinux it's the same thing.

  Configuration :
  Dell XPS 13 model 2019 (9380)
  Graphics chipset: Intel® UHD 620 (Whiskey Lake 3x8 GT2)

  Noted that this problem can occur regardless of the activity on the
  desktop (browser, video player...), sometimes the screen skips
  completely for a tenth of a second.

  Please correct the problem quickly

  
  capture1: https://nsa40.casimages.com/img/2019/09/17/190917050728230823.jpg
  capture2: https://nsa40.casimages.com/img/2019/09/17/190917050801231741.jpg
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon 22176 F pulseaudio
   /dev/snd/pcmC0D0p:   simon 22176 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-07-18 (60 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=d10cf0fc-051d-4ccd-b2da-e944d0ddd735 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2019-07-18T20:23:25.974818

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844384/+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 1850185] Re: [linux-azure] 19.04 regression of KDUMP

[Bryan Quigley]

** Tags added: sts

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

Title:
  [linux-azure] 19.04 regression of KDUMP

Status in linux-azure package in Ubuntu:
  New

Bug description:
  By default our test cases use DS1_v2 to test KDUMP, when we trigger a
  kernel panic, the VM enters into emergency mode, which can be seen on
  the serial console.

  This issue can be resolved if the VM is resized from DS1_v2 (1 vcpus,
  3.5 GiB memory) to DS12_v2 (4 vcpus, 28 GiB memory).  However, Ubuntu
  18.04 and Ubuntu 19.10 KDUMP work using a VM size of DS1_v2.  This
  issue only happens when using Ubuntu 19.04.

  The following appears on the 19.04 serial console when the issue
  occurs:

  [  OK  ] Reached target Local File Systems (Pre).
   Mounting /boot/efi...
   Starting File System Check…/cloud/azure_resource-part1...
  [FAILED] Failed to mount /boot/efi.
  See 'systemctl status boot-efi.mount' for details.
  [DEPEND] Dependency failed for Local File Systems.
  [  OK  ] Started File System Check …sk/cloud/azure_resource-part1.
  [  OK  ] Started File System Check Daemon to report status.
   Starting GRUB failed boot detection...
   Starting Create final runt…dir for shutdown pivot root...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  ] Started Emergency Shell.
   Starting Load AppArmor profiles...
   Starting Create Volatile Files and Directories...
  [  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
  [  OK  ] Reached target Emergency Mode.


  
  REPRO STEPS:
   
  Create Ubuntu 19.04 using size Standard_DS1_v2.
  Install kdump tools, reboot VM - apt update && apt install linux-crashdump, 
reboot VM, kdump-config show check the state is - ready to kdump.
  Trigger kernel panic - sysctl -w kernel.sysrq=1 && echo c > 
/proc/sysrq-trigger

  
  Expected behavior - VM reboot successfully and crash dump file and related 
subdirectories generated successfully.
  Current behavior - The VM is inaccessible from SSH, it enters into emergency 
mode, have to press Ctrl + D in serial console, then VM enters into normal 
reboot process, crash dump file and related subdirectories generated 
successfully.

  Update value for crashkernel to reserve the memory by updating the
  /etc/default/grub.d/kdump-tools.cfg file, run update-grub, reboot VM,
  dmesg | grep -i crashkernel check the memory is reserving successfully
  for crashkernel.

  Then retest (trigger kernel panic) against different memory setting
  for crashkernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1850185/+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 1848831] Re: Intel WiFi AX200 firmware loading error resulting in no wifi

[Zero_Chaos]

I'm not on ubuntu but I'm the same kernel with the same kernel bug and
same hardware.  Hope this helps anyway :-)


** Attachment added: "lspci -vvnk"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1848831/+attachment/5300949/+files/kernel-5.3.6.fail

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

Title:
  Intel WiFi AX200 firmware loading error resulting in no wifi

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

  uname -a
  Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  The card is detected OK as dmesg shows, however the card's firmware
  fails immediately after loading (see dmesg output below) and wifi
  doesn't work at all. Big disappointment since the AX200 chip was
  supposed to be supported on 19.10.

  Ubuntu includes two ax200 firmware versions, version 48 loads by
  default in my system (and fails). I tried version 46 (by renaming the
  version 48 file) and it failed in the exact same manner

  $ ls /lib/firmware/iwlwifi-cc-*
  /lib/firmware/iwlwifi-cc-a0-46.ucode  /lib/firmware/iwlwifi-cc-a0-48.ucode

  
  The card's Bluetooth functionality is also detected and it works fine. It's 
just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

  $ rfkill list
  0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no



  ~$ dmesg | grep iwl
  [   12.312443] iwlwifi :01:00.0: enabling device ( -> 0002)
  [   12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
43.2.23.17
  [   12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM
  [   12.321102] iwlwifi :01:00.0: Found debug configuration: 0
  [   12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 
op_mode iwlmvm
  [   12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, 
REV=0x340
  [   12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM
  [   12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [   13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired.
  [   13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414910] iwlwifi :01:00.0: Status: 0x, count: 6
  [   13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0
  [   13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [   13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0
  [   13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1
  [   13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1
  [   13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2
  [   13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1
  [   13.414917] iwlwifi :01:00.0: 0x1000 | data2
  [   13.414917] iwlwifi :01:00.0: 0xF000 | data3
  [   13.414918] iwlwifi :01:00.0: 0x | beacon time
  [   13.414919] iwlwifi :01:00.0: 0x795F | tsf low
  [   13.414919] iwlwifi :01:00.0: 0x | tsf hi
  [   13.414920] iwlwifi :01:00.0: 0x | time gp1
  [   13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2
  [   13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type
  [   13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major
  [   13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor
  [   13.414923] iwlwifi :01:00.0: 0x0340 | hw version
  [   13.414924] iwlwifi :01:00.0: 0x18C89000 | board version
  [   13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd
  [   13.414925] iwlwifi :01:00.0: 0x0002 | isr0
  [   13.414926] iwlwifi :01:00.0: 0x | isr1
  [   13.414926] iwlwifi :01:00.0: 0x08F2 | isr2
  [   13.414927] iwlwifi :01:00.0: 0x00CC | isr3
  [   13.414928] iwlwifi :01:00.0: 0x | isr4
  [   13.414928] iwlwifi :01:00.0: 0x | last cmd Id
  [   13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event
  [   13.414930] iwlwifi :01:00.0: 0x | l2p_control
  [   13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration
  [   13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid
  [   13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match
  [   13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel
  [   13.414933] iwlwifi :01:00.0: 0x | timestamp
  [   13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler
  [   13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [   13.414975] iwlwifi :01:00.0: Status: 0x, count: 7
  [   13.414976] iwlwifi :01:00.0: 0x201000A3 | ADVANCED_SYSASSERT
  [   13.414976] iwlwifi :01:00.0: 0x | umac branchlink1
  [   13.414977] iwlwifi :01:00.0: 

[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
-   bionic/linux/pc-kernel: bug 1849005, bug 1849852
-   bionic/linux/pc-lowlatency-kernel: bug 1849853, bug 1849006
+   bionic/linux/pc-kernel: bug 1849852, bug 1849005
+   bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849852, bug 1849005
bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850185] [NEW] [linux-azure] 19.04 regression of KDUMP

[Joseph Salisbury]

Public bug reported:

By default our test cases use DS1_v2 to test KDUMP, when we trigger a
kernel panic, the VM enters into emergency mode, which can be seen on
the serial console.

This issue can be resolved if the VM is resized from DS1_v2 (1 vcpus,
3.5 GiB memory) to DS12_v2 (4 vcpus, 28 GiB memory).  However, Ubuntu
18.04 and Ubuntu 19.10 KDUMP work using a VM size of DS1_v2.  This issue
only happens when using Ubuntu 19.04.

The following appears on the 19.04 serial console when the issue occurs:

[  OK  ] Reached target Local File Systems (Pre).
 Mounting /boot/efi...
 Starting File System Check…/cloud/azure_resource-part1...
[FAILED] Failed to mount /boot/efi.
See 'systemctl status boot-efi.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[  OK  ] Started File System Check …sk/cloud/azure_resource-part1.
[  OK  ] Started File System Check Daemon to report status.
 Starting GRUB failed boot detection...
 Starting Create final runt…dir for shutdown pivot root...
 Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Emergency Shell.
 Starting Load AppArmor profiles...
 Starting Create Volatile Files and Directories...
[  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
[  OK  ] Reached target Emergency Mode.


REPRO STEPS:
 
Create Ubuntu 19.04 using size Standard_DS1_v2.
Install kdump tools, reboot VM - apt update && apt install linux-crashdump, 
reboot VM, kdump-config show check the state is - ready to kdump.
Trigger kernel panic - sysctl -w kernel.sysrq=1 && echo c > /proc/sysrq-trigger


Expected behavior - VM reboot successfully and crash dump file and related 
subdirectories generated successfully.
Current behavior - The VM is inaccessible from SSH, it enters into emergency 
mode, have to press Ctrl + D in serial console, then VM enters into normal 
reboot process, crash dump file and related subdirectories generated 
successfully.

Update value for crashkernel to reserve the memory by updating the
/etc/default/grub.d/kdump-tools.cfg file, run update-grub, reboot VM,
dmesg | grep -i crashkernel check the memory is reserving successfully
for crashkernel.

Then retest (trigger kernel panic) against different memory setting for
crashkernel.

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


** Tags: sts

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

Title:
  [linux-azure] 19.04 regression of KDUMP

Status in linux-azure package in Ubuntu:
  New

Bug description:
  By default our test cases use DS1_v2 to test KDUMP, when we trigger a
  kernel panic, the VM enters into emergency mode, which can be seen on
  the serial console.

  This issue can be resolved if the VM is resized from DS1_v2 (1 vcpus,
  3.5 GiB memory) to DS12_v2 (4 vcpus, 28 GiB memory).  However, Ubuntu
  18.04 and Ubuntu 19.10 KDUMP work using a VM size of DS1_v2.  This
  issue only happens when using Ubuntu 19.04.

  The following appears on the 19.04 serial console when the issue
  occurs:

  [  OK  ] Reached target Local File Systems (Pre).
   Mounting /boot/efi...
   Starting File System Check…/cloud/azure_resource-part1...
  [FAILED] Failed to mount /boot/efi.
  See 'systemctl status boot-efi.mount' for details.
  [DEPEND] Dependency failed for Local File Systems.
  [  OK  ] Started File System Check …sk/cloud/azure_resource-part1.
  [  OK  ] Started File System Check Daemon to report status.
   Starting GRUB failed boot detection...
   Starting Create final runt…dir for shutdown pivot root...
   Starting Tell Plymouth To Write Out Runtime Data...
  [  OK  ] Started Emergency Shell.
   Starting Load AppArmor profiles...
   Starting Create Volatile Files and Directories...
  [  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
  [  OK  ] Reached target Emergency Mode.


  
  REPRO STEPS:
   
  Create Ubuntu 19.04 using size Standard_DS1_v2.
  Install kdump tools, reboot VM - apt update && apt install linux-crashdump, 
reboot VM, kdump-config show check the state is - ready to kdump.
  Trigger kernel panic - sysctl -w kernel.sysrq=1 && echo c > 
/proc/sysrq-trigger

  
  Expected behavior - VM reboot successfully and crash dump file and related 
subdirectories generated successfully.
  Current behavior - The VM is inaccessible from SSH, it enters into emergency 
mode, have to press Ctrl + D in serial console, then VM enters into normal 
reboot process, crash dump file and related subdirectories generated 
successfully.

  Update value for crashkernel to reserve the memory by updating the
  /etc/default/grub.d/kdump-tools.cfg file, run update-grub, reboot VM,
  dmesg | grep -i crashkernel check the memory is reserving successfully
  for crashkernel.

  Then retest (trigger kernel panic) against 

[Kernel-packages] [Bug 1841485] Re: Unbearable whistling in headphones

[Philippe]

The problem is very old, nobody solved it ;(

This post from 2014 talk about similar whistling in headphones

https://askubuntu.com/questions/457910/strange-noise-in-headphones-when-
no-sound-is-played

The solution Below does not work well :


" Got the same problem on Dell XPS15 (9550, 2015 model in Xenial). Solved it in 
alsamixer and muting the loopback channel.

$ alsamixer
Navigating to loopback (all the way to the right, with → key) and setting it to 
Disabled using Mthe ↑ key. "

With Loopback Enable the whistling is his acute, with Loopback Disable
the song is low-pitched.

This is clearly Realtek ALC3266 driver problem...

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

Title:
  Unbearable whistling in headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unbearable whistling in headphones plugged into 3.5 mm audio jack
  port.

  My Dell XPS 9570 with the kernel 4.15.0-58 (LTS) & 5.0.0-25 are impacted by 
this bug ;(
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   philippe   2233 F...m pulseaudio
   /dev/snd/controlC0:  philippe   2233 F pulseaudio
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2019-08-26 (0 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=620f2477-363c-44a5-828d-b6d70149d781 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-58-generic N/A
   linux-backports-modules-4.15.0-58-generic  N/A
   linux-firmware 1.173.9
  Tags:  tina
  Uname: Linux 4.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841485/+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 1850135] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1850135

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

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

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

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

** Tags added: bionic

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

Title:
  mlx5: Tail padding HW Checksum crash in ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  we have the following issue which affects a lot of our customers this issue 
fixes upstream and need to add the fixes to ubuntu 18.04.

  Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
  4.15.0-58-generic.

  Crach log:

  [Fri Aug 30 07:15:23 2019] enp59s0f0.101: hw csum failure
  [Fri Aug 30 07:15:23 2019] CPU: 40 PID: 0 Comm: swapper/40 Not tainted 
4.15.0-58-generic #64-Ubuntu
  [Fri Aug 30 07:15:23 2019] Hardware name: Supermicro 
SYS-2029BT-A2-ADBE-FS011/X11DPT-B, BIOS 3.1 04/30/2019
  [Fri Aug 30 07:15:23 2019] Call Trace:
  [Fri Aug 30 07:15:23 2019] 
  [Fri Aug 30 07:15:23 2019] dump_stack+0x63/0x8b
  [Fri Aug 30 07:15:23 2019] netdev_rx_csum_fault+0x38/0x40
  [Fri Aug 30 07:15:23 2019] __skb_checksum_complete+0xbc/0xd0
  [Fri Aug 30 07:15:23 2019] nf_ip_checksum+0xc3/0xf0
  [Fri Aug 30 07:15:23 2019] tcp_error+0x162/0x1c0 [nf_conntrack]
  [Fri Aug 30 07:15:23 2019] ? update_load_avg+0x57f/0x6e0
  [Fri Aug 30 07:15:23 2019] ? __update_load_avg_se.isra.38+0x1c0/0x1d0
  [Fri Aug 30 07:15:23 2019] nf_conntrack_in+0x14f/0x500 [nf_conntrack]
  [Fri Aug 30 07:15:23 2019] ? csum_partial_ext+0x9/0x10
  [Fri Aug 30 07:15:23 2019] ? __skb_checksum+0x6b/0x300
  [Fri Aug 30 07:15:23 2019] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
  [Fri Aug 30 07:15:23 2019] nf_hook_slow+0x48/0xc0
  [Fri Aug 30 07:15:23 2019] ? skb_send_sock+0x50/0x50
  [Fri Aug 30 07:15:23 2019] ip_rcv+0x2fa/0x360
  [Fri Aug 30 07:15:23 2019] ? inet_del_offload+0x40/0x40
  [Fri Aug 30 07:15:23 2019] __netif_receive_skb_core+0x432/0xb40
  [Fri Aug 30 07:15:23 2019] ? tcp4_gro_receive+0x137/0x1a0
  [Fri Aug 30 07:15:23 2019] __netif_receive_skb+0x18/0x60
  [Fri Aug 30 07:15:23 2019] ? __netif_receive_skb+0x18/0x60
  [Fri Aug 30 07:15:23 2019] netif_receive_skb_internal+0x45/0xe0
  [Fri Aug 30 07:15:23 2019] napi_gro_receive+0xc5/0xf0
  [Fri Aug 30 07:15:23 2019] mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] net_rx_action+0x140/0x3a0
  [Fri Aug 30 07:15:23 2019] __do_softirq+0xe4/0x2d4
  [Fri Aug 30 07:15:23 2019] irq_exit+0xc5/0xd0
  [Fri Aug 30 07:15:23 2019] do_IRQ+0x8a/0xe0
  [Fri Aug 30 07:15:23 2019] common_interrupt+0x8c/0x8c
  [Fri Aug 30 07:15:23 2019] 
  [Fri Aug 30 07:15:23 2019] RIP: 0010:cpu_idle_poll+0x3b/0x14


  
  additional info:
  this issue fixed upstream by the following patches list:
net/mlx5e: Rx, Fix checksum calculation for new hardware -->  
db849faa9bef993a1379dc510623f750a72fa7ce
net/mlx5e: Rx, Check ip headers sanity - > 
0318a7b7fcad9765931146efa7ca3a034194737c
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding -->  
0aa1d18615c163f92935b806dcaff9157645233a
net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded --> 
5d0bb3bac4b9f6c22280b04545626fdfd99edc6b
mlx5: fix get_ip_proto() --> ef6fcd455278c2be3032a346cc66d9dd9866b787
net/mlx5e: Allow reporting of checksum unnecessary -->   
b856df28f9230a47669efbdd57896084caadb2b3
net/mlx5e: don't set CHECKSUM_COMPLETE on SCTP packets --> 
fe1dc069990c1f290ef6b99adb46332c03258f38
net/mlx5e: Set ECN for received packets using CQE indication --> 
f007c13d4ad62f494c83897eda96437005df4a91
net/mlx5e: Add likely to the common RX checksum flow --> 
63a612f984a1fae040ab6f1c6a0f1fdcdf1954b8  --> taking
net/mlx5e: CHECKSUM_COMPLETE offload for VLAN/QinQ packets -->  
f938daeee95eb36ef6b431bf054a5cc6cdada112 --> in ubuntu 

  we trying to backport those patches list to bionic kernel master
  branch, will add the adjusted patches once the backporting is done.

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

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

[Kernel-packages] [Bug 1850175] Re: update ENA driver to version 2.1.0

[Kamal Mostafa]

** Description changed:

  Update the Amazon ENA driver to version 2.1.0 from mainline.
+ 
+ Port all ENA driver commits up to this:
+ dbbc6e687776 net: ena: update driver version from 2.0.3 to 2.1.0
+ ...
+ 
+ And also these specific commits after 2.1.0
+ 4208966f65f5 net: ena: clean up indentation issue
+ a53651ec93a8 net: ena: don't wake up tx queue when down
+ eb203bae834e Revert "net: ena: ethtool: add extra properties retrieval via 
get_priv_flags"
+ 3e5bfb189e1a net: ena: Fix bug where ring allocation backoff stopped too late
+ 
+ (Note eoan already carries all but two of these).

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  update ENA driver to version 2.1.0

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New

Bug description:
  Update the Amazon ENA driver to version 2.1.0 from mainline.

  Port all ENA driver commits up to this:
  dbbc6e687776 net: ena: update driver version from 2.0.3 to 2.1.0
  ...

  And also these specific commits after 2.1.0
  4208966f65f5 net: ena: clean up indentation issue
  a53651ec93a8 net: ena: don't wake up tx queue when down
  eb203bae834e Revert "net: ena: ethtool: add extra properties retrieval via 
get_priv_flags"
  3e5bfb189e1a net: ena: Fix bug where ring allocation backoff stopped too late

  (Note eoan already carries all but two of these).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850175/+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 1848212] Re: Optane PM access times are much longer than they should be

[steve heller]

This seems to be working correctly now here:

https://lore.kernel.org/linux-nvdimm/CAPcyv4gi--MyxXOt-
vb4Tw+ku=juymo4y+ysv+6ujf24bcd...@mail.gmail.com/

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

Title:
  Optane PM access times are much longer than they should be

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have 4 128GB Optane DC Persistent Memory devices in my server,
  assigned to AppDirect access (i.e., accessed via memory-mapping at the
  cache line level), and have run into a severe performance issue with
  the latest kernel 5.0.0-31.

  I realize that not many people have this storage type as yet, but it
  is becoming increasingly important in the server world, so I think
  this bug is pretty important.

  Bug details:

  When running with kernel 5.0.0-29, write access times to the Optane PM
  devices are in the sub-microsecond range, as they should be.

  When running with kernel 5.0.0-31, write access times are much slower,
  averaging in the 30 microsecond range, until a large number of writes
  (see below) have been executed. Then they return to normal speed.

  My application is a hash table implementation optimized for the Optane
  PM devices (see webpage at www.threemisses.com). Since it is a hash
  table, it has very poor locality of reference, and is filled
  "randomly", so I don't know exactly what the sequence of writes is.

  However, I can say that the speed is very slow until the fill ratio of
  the hash table is about 50%, then it returns to the normal sub-
  microsecond range.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Oct 15 09:01:06 2019
  InstallationDate: Installed on 2019-09-02 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.

   eno0  no wireless extensions.

   enp181s0f1  no wireless extensions.
  MachineType: Supermicro SYS-7039A-I
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=3239f211-86a3-44bb-8251-62037ebea848 ro transparent_hugepage=always 
quiet splash nomodeset vt.handoff=1
  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.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: ZM193S000653
  dmi.board.name: X11DAi-N
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd03/06/2019:svnSupermicro:pnSYS-7039A-I:pvr123456789:rvnSupermicro:rnX11DAi-N:rvr1.02:cvnSupermicro:ct1:cvr123456789:
  dmi.product.family: SMC X11
  dmi.product.name: SYS-7039A-I
  dmi.product.sku: 097A15D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848212/+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 1850175] [NEW] update ENA driver to version 2.1.0

[Kamal Mostafa]

Public bug reported:

Update the Amazon ENA driver to version 2.1.0 from mainline.

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

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

Title:
  update ENA driver to version 2.1.0

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Update the Amazon ENA driver to version 2.1.0 from mainline.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850175/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
-   bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
+   bionic/linux/pc-lowlatency-kernel: bug 1849853, bug 1849006
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849853, bug 1849006
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850066] Re: [Star LabTop (Mk III)] Screen backlight pulses rapidly when cursor is still.

[Fiona Hinman]

The brightness number does not seem to fluctuate, so it might be a
different issue than the backlight that creates the pulsing effect.

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

Title:
  [Star LabTop (Mk III)] Screen backlight pulses rapidly when cursor is
  still.

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  The backlight for my display appears to brighten and dim rapidly
  whenever the mouse cursor is still, but stops when the cursor is being
  moved. The pulsing backlight is distracting and causes eye strain.
  Same issue experienced on Ubuntu 19.04 before upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 27 13:08:24 2019
  DistUpgraded: 2019-10-22 00:34:33,817 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation UHD Graphics 620 [8086:5917]
  InstallationDate: Installed on 2019-10-08 (19 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 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2085 Sunplus Innovation Technology Inc. HP HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs LabTop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=f6561506-cd05-4022-b582-c38a0a405d1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (5 days ago)
  dmi.bios.date: 07/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.0.09
  dmi.board.asset.tag: Default string
  dmi.board.name: Star LabTop (Mk III)
  dmi.board.vendor: Star Labs Online Limited
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.0.09:bd07/05/2019:svnStarLabs:pnLabTop:pvrDefaultstring:rvnStarLabsOnlineLimited:rnStarLabTop(MkIII):rvrDefaultstring:cvnStarLabs:ct10:cvrDefaultstring:
  dmi.product.family: KBLR_NB_133
  dmi.product.name: LabTop
  dmi.product.sku: L3-U
  dmi.product.version: Default string
  dmi.sys.vendor: Star Labs
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fiona  1724 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-08 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Star Labs LabTop
  Package: mutter 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  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-19-generic 
root=UUID=f6561506-cd05-4022-b582-c38a0a405d1b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev 

[Kernel-packages] [Bug 1845033] Re: xenbus: Avoid deadlock during suspend due to open transactions

[Kamal Mostafa]

I have set this bug as "not a duplicate", in order to track the request
to have the fix backported to the 4.4 kernels (Xenial and Trusty-hwe ).

** This bug is no longer a duplicate of bug 1840076
   Disco update: upstream stable patchset 2019-08-13

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

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

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
   Status: New => 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/1845033

Title:
  xenbus: Avoid deadlock during suspend due to open transactions

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Xen guests may hang during resume after a migration or suspend.

  [Test Case]
  Create a Xen guest and run this script and then suspending the VM:

  import pyxs, time
  c = pyxs.client.Client(xen_bus_path="/dev/xen/xenbus")
  c.connect()
  c.transaction()
  time.sleep(3600)

  [Fix]
  The following upstream commit fixes the issue:

  "xenbus: Avoid deadlock during suspend due to open transactions"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d10e0cc113c9e1b64b5c6e3db37b5c839794f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845033/+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 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

[Mark Dunn]

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

I have a PI 4 (4GB)

I loaded and installed the arm64 eoan 
USB didn't work, ssh did

I set total_mem=1024
USB worked

I set total_mem=3072
USB failed

I set total_mem=1024 and loaded the linux image:
wget 
https://people.canonical.com/~hwang4/rpiv2/arm64/linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
wget 
https://people.canonical.com/~hwang4/rpiv2/arm64/linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb

sudo dpkg -i linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo dpkg -i linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo reboot

USB Worked

I commented out the total_mem=3072
USB failed

I believe the following will help:

In the raspberry pi git (4.19.y)
https://github.com/raspberrypi/linux/issues/3093

hitmoon commented on 12 Aug
"I've created a trivial patch to add bounce buffers on ARM64 for 
pcie-bcrmstb.
pcie-brcmstb-bounce64.patch.zip

I tried this patch, it works for me!
All 4G memory is alive now, COOL !! :-)
Thanks @yaroslavros !

This fixed my linux image for my home rolled 19.04 ubuntu so I hope it
fixes yours

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Pi 4 new install.  System boots up but USB bus is not working.

  Tried 3 keyboards no key presses detected, 2 usb memory drives don't
  show up in lsblk.

  output of $lspci
  00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10)
  01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller 
(rev 01) 

  output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or
  attached to this bug report.

  Not the only one experiencing bug.  Another user created a post on the ubuntu 
forums: 
  
https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142


  64bit raspberry pi 4&4 image pulled from
  https://ubuntu.com/download/iot/raspberry-pi page.  Specifically
  http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10
  -preinstalled-server-arm64+raspi3.img.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+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 1850135] Re: mlx5: Tail padding HW Checksum crash in ubuntu 18.04

[Brian Murray]

** 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/1850135

Title:
  mlx5: Tail padding HW Checksum crash in ubuntu 18.04

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  we have the following issue which affects a lot of our customers this issue 
fixes upstream and need to add the fixes to ubuntu 18.04.

  Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
  4.15.0-58-generic.

  Crach log:

  [Fri Aug 30 07:15:23 2019] enp59s0f0.101: hw csum failure
  [Fri Aug 30 07:15:23 2019] CPU: 40 PID: 0 Comm: swapper/40 Not tainted 
4.15.0-58-generic #64-Ubuntu
  [Fri Aug 30 07:15:23 2019] Hardware name: Supermicro 
SYS-2029BT-A2-ADBE-FS011/X11DPT-B, BIOS 3.1 04/30/2019
  [Fri Aug 30 07:15:23 2019] Call Trace:
  [Fri Aug 30 07:15:23 2019] 
  [Fri Aug 30 07:15:23 2019] dump_stack+0x63/0x8b
  [Fri Aug 30 07:15:23 2019] netdev_rx_csum_fault+0x38/0x40
  [Fri Aug 30 07:15:23 2019] __skb_checksum_complete+0xbc/0xd0
  [Fri Aug 30 07:15:23 2019] nf_ip_checksum+0xc3/0xf0
  [Fri Aug 30 07:15:23 2019] tcp_error+0x162/0x1c0 [nf_conntrack]
  [Fri Aug 30 07:15:23 2019] ? update_load_avg+0x57f/0x6e0
  [Fri Aug 30 07:15:23 2019] ? __update_load_avg_se.isra.38+0x1c0/0x1d0
  [Fri Aug 30 07:15:23 2019] nf_conntrack_in+0x14f/0x500 [nf_conntrack]
  [Fri Aug 30 07:15:23 2019] ? csum_partial_ext+0x9/0x10
  [Fri Aug 30 07:15:23 2019] ? __skb_checksum+0x6b/0x300
  [Fri Aug 30 07:15:23 2019] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
  [Fri Aug 30 07:15:23 2019] nf_hook_slow+0x48/0xc0
  [Fri Aug 30 07:15:23 2019] ? skb_send_sock+0x50/0x50
  [Fri Aug 30 07:15:23 2019] ip_rcv+0x2fa/0x360
  [Fri Aug 30 07:15:23 2019] ? inet_del_offload+0x40/0x40
  [Fri Aug 30 07:15:23 2019] __netif_receive_skb_core+0x432/0xb40
  [Fri Aug 30 07:15:23 2019] ? tcp4_gro_receive+0x137/0x1a0
  [Fri Aug 30 07:15:23 2019] __netif_receive_skb+0x18/0x60
  [Fri Aug 30 07:15:23 2019] ? __netif_receive_skb+0x18/0x60
  [Fri Aug 30 07:15:23 2019] netif_receive_skb_internal+0x45/0xe0
  [Fri Aug 30 07:15:23 2019] napi_gro_receive+0xc5/0xf0
  [Fri Aug 30 07:15:23 2019] mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
  [Fri Aug 30 07:15:23 2019] net_rx_action+0x140/0x3a0
  [Fri Aug 30 07:15:23 2019] __do_softirq+0xe4/0x2d4
  [Fri Aug 30 07:15:23 2019] irq_exit+0xc5/0xd0
  [Fri Aug 30 07:15:23 2019] do_IRQ+0x8a/0xe0
  [Fri Aug 30 07:15:23 2019] common_interrupt+0x8c/0x8c
  [Fri Aug 30 07:15:23 2019] 
  [Fri Aug 30 07:15:23 2019] RIP: 0010:cpu_idle_poll+0x3b/0x14


  
  additional info:
  this issue fixed upstream by the following patches list:
net/mlx5e: Rx, Fix checksum calculation for new hardware -->  
db849faa9bef993a1379dc510623f750a72fa7ce
net/mlx5e: Rx, Check ip headers sanity - > 
0318a7b7fcad9765931146efa7ca3a034194737c
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding -->  
0aa1d18615c163f92935b806dcaff9157645233a
net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded --> 
5d0bb3bac4b9f6c22280b04545626fdfd99edc6b
mlx5: fix get_ip_proto() --> ef6fcd455278c2be3032a346cc66d9dd9866b787
net/mlx5e: Allow reporting of checksum unnecessary -->   
b856df28f9230a47669efbdd57896084caadb2b3
net/mlx5e: don't set CHECKSUM_COMPLETE on SCTP packets --> 
fe1dc069990c1f290ef6b99adb46332c03258f38
net/mlx5e: Set ECN for received packets using CQE indication --> 
f007c13d4ad62f494c83897eda96437005df4a91
net/mlx5e: Add likely to the common RX checksum flow --> 
63a612f984a1fae040ab6f1c6a0f1fdcdf1954b8  --> taking
net/mlx5e: CHECKSUM_COMPLETE offload for VLAN/QinQ packets -->  
f938daeee95eb36ef6b431bf054a5cc6cdada112 --> in ubuntu 

  we trying to backport those patches list to bionic kernel master
  branch, will add the adjusted patches once the backporting is done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850135/+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 1840076] Re: Disco update: upstream stable patchset 2019-08-13

[Kamal Mostafa]

I've re-opened 1845033 (for Xenial) to track this request.

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

Title:
  Disco update: upstream stable patchset 2019-08-13

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

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

     upstream stable patchset 2019-08-13

  Ported from the following upstream stable releases:
  v4.19.53, v5.1.12,
  v4.19.54, v5.1.13,
  v4.19.55, v5.1.14,

     from git://git.kernel.org/

  UBUNTU: [Config] updateconfigs for CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT
  drm/nouveau: add kconfig option to turn off nouveau legacy contexts. (v3)
  nouveau: Fix build with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT disabled
  HID: multitouch: handle faulty Elo touch device
  HID: wacom: Don't set tool type until we're in range
  HID: wacom: Don't report anything prior to the tool entering range
  HID: wacom: Send BTN_TOUCH in response to INTUOSP2_BT eraser contact
  HID: wacom: Correct button numbering 2nd-gen Intuos Pro over Bluetooth
  HID: wacom: Sync INTUOSP2_BT touch state after each frame if necessary
  ALSA: oxfw: allow PCM capture for Stanton SCS.1m
  ALSA: hda/realtek - Update headset mode for ALC256
  ALSA: firewire-motu: fix destruction of data for isochronous resources
  libata: Extend quirks for the ST1000LM024 drives with NOLPM quirk
  mm/list_lru.c: fix memory leak in __memcg_init_list_lru_node
  fs/ocfs2: fix race in ocfs2_dentry_attach_lock()
  mm/vmscan.c: fix trying to reclaim unevictable LRU page
  signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO
  ptrace: restore smp_rmb() in __ptrace_may_access()
  iommu/arm-smmu: Avoid constant zero in TLBI writes
  i2c: acorn: fix i2c warning
  bcache: fix stack corruption by PRECEDING_KEY()
  cgroup: Use css_tryget() instead of css_tryget_online() in task_get_css()
  ASoC: cs42xx8: Add regcache mask dirty
  ASoC: fsl_asrc: Fix the issue about unsupported rate
  drm/i915/sdvo: Implement proper HDMI audio support for SDVO
  x86/uaccess, kcov: Disable stack protector
  ALSA: seq: Protect in-kernel ioctl calls with mutex
  ALSA: seq: Fix race of get-subscription call vs port-delete ioctls
  Revert "ALSA: seq: Protect in-kernel ioctl calls with mutex"
  s390/kasan: fix strncpy_from_user kasan checks
  Drivers: misc: fix out-of-bounds access in function param_set_kgdbts_var
  f2fs: fix to avoid accessing xattr across the boundary
  scsi: qedi: remove memset/memcpy to nfunc and use func instead
  scsi: qedi: remove set but not used variables 'cdev' and 'udev'
  scsi: lpfc: correct rcu unlock issue in lpfc_nvme_info_show
  scsi: lpfc: add check for loss of ndlp when sending RRQ
  arm64/mm: Inhibit huge-vmap with ptdump
  nvme: fix srcu locking on error return in nvme_get_ns_from_disk
  nvme: remove the ifdef around nvme_nvm_ioctl
  nvme: merge nvme_ns_ioctl into nvme_ioctl
  nvme: release namespace SRCU protection before performing controller ioctls
  nvme: fix memory leak for power latency tolerance
  platform/x86: pmc_atom: Add Lex 3I380D industrial PC to critclk_systems DMI 
table
  platform/x86: pmc_atom: Add several Beckhoff Automation boards to 
critclk_systems DMI table
  scsi: bnx2fc: fix incorrect cast to u64 on shift operation
  libnvdimm: Fix compilation warnings with W=1
  selftests/timers: Add missing fflush(stdout) calls
  tracing: Prevent hist_field_var_ref() from accessing NULL tracing_map_elts
  usbnet: ipheth: fix racing condition
  KVM: arm/arm64: Move cc/it checks under hyp's Makefile to avoid 
instrumentation
  KVM: x86/pmu: mask the result of rdpmc according to the width of the counters
  KVM: x86/pmu: do not mask the value that is written to fixed PMUs
  KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION
  tools/kvm_stat: fix fields filter for child events
  drm/vmwgfx: integer underflow in vmw_cmd_dx_set_shader() leading to an 
invalid read
  drm/vmwgfx: NULL pointer dereference from vmw_cmd_dx_view_define()
  usb: dwc2: Fix DMA cache alignment issues
  usb: dwc2: host: Fix wMaxPacketSize handling (fix webcam regression)
  USB: Fix chipmunk-like voice when using Logitech C270 for recording audio.
  USB: serial: pl2303: add Allied Telesis VT-Kit3
  USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
  USB: serial: option: add Telit 0x1260 and 

[Kernel-packages] [Bug 1850135] [NEW] mlx5: Tail padding HW Checksum crash in ubuntu 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi,
we have the following issue which affects a lot of our customers this issue 
fixes upstream and need to add the fixes to ubuntu 18.04.

Mlx5 driver: Tail padding HW Checksum crash in Ubuntu 18.04 kernel
4.15.0-58-generic.

Crach log:

[Fri Aug 30 07:15:23 2019] enp59s0f0.101: hw csum failure
[Fri Aug 30 07:15:23 2019] CPU: 40 PID: 0 Comm: swapper/40 Not tainted 
4.15.0-58-generic #64-Ubuntu
[Fri Aug 30 07:15:23 2019] Hardware name: Supermicro 
SYS-2029BT-A2-ADBE-FS011/X11DPT-B, BIOS 3.1 04/30/2019
[Fri Aug 30 07:15:23 2019] Call Trace:
[Fri Aug 30 07:15:23 2019] 
[Fri Aug 30 07:15:23 2019] dump_stack+0x63/0x8b
[Fri Aug 30 07:15:23 2019] netdev_rx_csum_fault+0x38/0x40
[Fri Aug 30 07:15:23 2019] __skb_checksum_complete+0xbc/0xd0
[Fri Aug 30 07:15:23 2019] nf_ip_checksum+0xc3/0xf0
[Fri Aug 30 07:15:23 2019] tcp_error+0x162/0x1c0 [nf_conntrack]
[Fri Aug 30 07:15:23 2019] ? update_load_avg+0x57f/0x6e0
[Fri Aug 30 07:15:23 2019] ? __update_load_avg_se.isra.38+0x1c0/0x1d0
[Fri Aug 30 07:15:23 2019] nf_conntrack_in+0x14f/0x500 [nf_conntrack]
[Fri Aug 30 07:15:23 2019] ? csum_partial_ext+0x9/0x10
[Fri Aug 30 07:15:23 2019] ? __skb_checksum+0x6b/0x300
[Fri Aug 30 07:15:23 2019] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
[Fri Aug 30 07:15:23 2019] nf_hook_slow+0x48/0xc0
[Fri Aug 30 07:15:23 2019] ? skb_send_sock+0x50/0x50
[Fri Aug 30 07:15:23 2019] ip_rcv+0x2fa/0x360
[Fri Aug 30 07:15:23 2019] ? inet_del_offload+0x40/0x40
[Fri Aug 30 07:15:23 2019] __netif_receive_skb_core+0x432/0xb40
[Fri Aug 30 07:15:23 2019] ? tcp4_gro_receive+0x137/0x1a0
[Fri Aug 30 07:15:23 2019] __netif_receive_skb+0x18/0x60
[Fri Aug 30 07:15:23 2019] ? __netif_receive_skb+0x18/0x60
[Fri Aug 30 07:15:23 2019] netif_receive_skb_internal+0x45/0xe0
[Fri Aug 30 07:15:23 2019] napi_gro_receive+0xc5/0xf0
[Fri Aug 30 07:15:23 2019] mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core]
[Fri Aug 30 07:15:23 2019] mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core]
[Fri Aug 30 07:15:23 2019] mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
[Fri Aug 30 07:15:23 2019] net_rx_action+0x140/0x3a0
[Fri Aug 30 07:15:23 2019] __do_softirq+0xe4/0x2d4
[Fri Aug 30 07:15:23 2019] irq_exit+0xc5/0xd0
[Fri Aug 30 07:15:23 2019] do_IRQ+0x8a/0xe0
[Fri Aug 30 07:15:23 2019] common_interrupt+0x8c/0x8c
[Fri Aug 30 07:15:23 2019] 
[Fri Aug 30 07:15:23 2019] RIP: 0010:cpu_idle_poll+0x3b/0x14



additional info:
this issue fixed upstream by the following patches list:
net/mlx5e: Rx, Fix checksum calculation for new hardware -->  
db849faa9bef993a1379dc510623f750a72fa7ce
net/mlx5e: Rx, Check ip headers sanity - > 
0318a7b7fcad9765931146efa7ca3a034194737c
net/mlx5e: Rx, Fixup skb checksum for packets with tail padding -->  
0aa1d18615c163f92935b806dcaff9157645233a
net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded --> 
5d0bb3bac4b9f6c22280b04545626fdfd99edc6b
mlx5: fix get_ip_proto() --> ef6fcd455278c2be3032a346cc66d9dd9866b787
net/mlx5e: Allow reporting of checksum unnecessary -->   
b856df28f9230a47669efbdd57896084caadb2b3
net/mlx5e: don't set CHECKSUM_COMPLETE on SCTP packets --> 
fe1dc069990c1f290ef6b99adb46332c03258f38
net/mlx5e: Set ECN for received packets using CQE indication --> 
f007c13d4ad62f494c83897eda96437005df4a91
net/mlx5e: Add likely to the common RX checksum flow --> 
63a612f984a1fae040ab6f1c6a0f1fdcdf1954b8  --> taking
net/mlx5e: CHECKSUM_COMPLETE offload for VLAN/QinQ packets -->  
f938daeee95eb36ef6b431bf054a5cc6cdada112 --> in ubuntu 

we trying to backport those patches list to bionic kernel master branch,
will add the adjusted patches once the backporting is done.

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


** Tags: bot-comment kernel-bug
-- 
mlx5: Tail padding HW Checksum crash in ubuntu 18.04
https://bugs.launchpad.net/bugs/1850135
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 1612916] Re: Internal speakers don't work after standby

[Christopher M. Penalver]

Michael, it wouldn't hurt to update your BIOS to the latest (now. 6.30),
given it includes multiple, high severity security vulnerability fixes.

Once done, could you please advise if this changes anything, and post the 
results of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

If still reproducible, to keep this relevant, please attempt a suspend
via live environment of http://cdimage.ubuntu.com/daily-live/current/
and advise on the outcome.

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

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

** Summary changed:

- Internal speakers don't work after standby
+ [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

** Description changed:

- I've a Toshiba x20t-C-121 (Skylake m7-6Y75 based). On initial boot,
- sound on internal speakers is working. After standby it doesn work
- anymore, but a analog headset does. Switching around in pavucontrol
- doesn't work... Internal microphone works.
+ On initial boot, sound on internal speakers is working. After standby it
+ doesn work anymore, but a analog headset does. Switching around in
+ pavucontrol doesn't work... Internal microphone works.
  
  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.
+ 
+ Toshiba/Dynabook Portege Z20T-C:
+ 
https://support.dynabook.com/support/modelHome?freeText=1200015981=785
+ 
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  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.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  

[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error

[Andrew Cloke]

Next steps: wait for the patch to land in Eoan -updates, and then
propose SRU for bionic and disco.

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

Title:
  [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check
  Error

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  In Progress

Bug description:
  [IMPACT]
  MCE test renders the system unresponsive on P9 open power hardware 
(Withersoon)

  [TEST]
  A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see 
the [OTHER] section for test details and comment #7 for results with the PPA 
kernel. 

  [FIX]
  IBM has identified the following patch that fixes this issue:
  commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee
  Author: Balbir Singh 
  Date:   Tue Aug 20 13:43:47 2019 +0530

  powerpc/mce: Fix MCE handling for huge pages

  [REGRESSION POTENTIAL]
  The patch is applicable the powerpc architecture and limited in scope to MCE 
handling for huge pages. Patch does not touch any generic code. Regression if 
any is limited to powerpc MCE handling.

  [OTHER]
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-05-07 
23:31:20 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images built  
from the upstream op-build git tree.

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
   open-power-witherspoon-v2.3-rc2-58-g59fd0743
  buildroot-2019.02.2-17-g93b841d204
  skiboot-v6.3-rc2
  hostboot-19a436e
  occ-58e422d
  linux-5.0.9-openpower1-p3a4d5a4
  petitboot-v1.10.3
  machine-xml-a6f4df3
  hostboot-binaries-hw043019a.940
  capp-ucode-p9-dd2-v4
  sbe-249671d
  hcode-hw040319a.940

  Then enable sw xstop manually by using below command:

  root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable
  root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config
  "ibm,skiboot" Partition
  --
  experimental-fast-reset=1
  snarf-mode=noo
  opal-sw-xstop=enable

  Then from the Linux HOST injected the MCE UE Error on the machine as
  follows:

  root@ltc-wspoon11:~# ./probe_cpus.sh -L
  CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs:  0 1 2 3
  CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs:  4 5 6 7
  CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs:  8 9 10 11
  CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs:  12 13 14 15
  CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs:  16 17 18 19
  CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs:  20 21 22 23
  CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs:  24 25 26 27
  CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs:  28 29 30 31
  CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs:  32 33 34 35
  CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs:  36 37 38 39
  CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs:  40 41 42 43
  CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs:  44 45 46 47
  CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs:  48 49 50 51
  CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs:  52 53 54 55
  CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs:  56 57 58 59
  CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs:  60 61 62 63
  CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs:  64 65 66 67
  CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs:  68 69 70 71
  CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs:  72 73 74 75
  CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs:  76 77 78 79
  CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs:  80 81 82 83
  CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs:  84 85 86 87
  CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs:  88 89 90 91
  CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs:  92 93 94 95
  CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs:  96 97 98 99
  CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs:  100 101 102 103
  CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs:  104 105 106 107
  CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs:  108 109 110 111
  CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs:  112 113 114 115
  CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs:  116 117 118 119
  CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs:  120 121 122 123
  CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs:  124 125 126 127
  CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs:  128 129 130 131
  CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs:  132 133 134 135
  CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs:  136 137 138 139
  CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs:  140 141 142 143

  -
  p[0]
     eq[0,1,2,3,4,5]
     ex[0,1,3,4,5,6,8,9,10]
  c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21]
  p[8]
     eq[1,2,3,4,5]
     

[Kernel-packages] [Bug 1612916] Re: Internal speakers don't work after standby

[Christopher M. Penalver]

** Tags removed: kernel-bug-exists-upstream latest-bios-5.60
** Tags added: bios-outdated-6.30 needs-upstream-testing

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  I've a Toshiba x20t-C-121 (Skylake m7-6Y75 based). On initial boot,
  sound on internal speakers is working. After standby it doesn work
  anymore, but a analog headset does. Switching around in pavucontrol
  doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  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.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 1801540]

[bkrippner]

Confirming this for ALC887-VD Analog [ALC887-VD Analog]

Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia
Controller [1022:780d] (rev 01)

Crackling seems to only go away when mix is set to lower than 10% in
pulseaudio. If the device oversaturates it seems to try to lower the
volume and starts to crackle for a while making it unusable to record or
talk for a long time. This has been around for a long time now.

It seems there is already a patch but im kinda worried by the version
number. 5.3.x seems pretty far away from stable
releases(5.0.0-27-generic)?

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Łukasz Zemczak]

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

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 992778] Re: Dual Monitor Freeze after changing Display Settings in ubuntu 12.04

[Christopher M. Penalver]

Medya, this report is being closed as no debugging logs regarding your
problem have been provided by you, as requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/992778/comments/43
.

However, if this is still reproducible in a supported release, please
follow the previous instructions, and mark this report as Status New.

** Description changed:

  I had 11.10 64bit, I upgraded to 12.04
  
  if I change the settings in the Display it will freeze .
  -  if I move the external monitor  to the left of laptop monitor , (or above 
it) it will freeze
-  - if I try to turn of the laptop monitor ,so I only have my external monitor 
it will freeze again.
+  - if I try to turn of the laptop monitor ,so I only have my external monitor 
it will freeze again.
  
  the mouse wont move and I have to reset the computer by ALT PRINT K to
  come back to ubuntu
  
- dual monitor used to work fine in ubuntu 11.10 , is there any way to 
downgrade the Display program to the one in 11.10 ?
- --- 
+ dual monitor used to work fine in ubuntu 11.10 , is there any way to
+ downgrade the Display program to the one in 11.10 ?
+ 
+ WORKAROUND: Install packages from
+ https://launchpad.net/~sarvatt/+archive/sru1/+build/3118994
+ 
+ ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-meta
  Tags:  precise precise
  Uname: Linux 3.3.0-030300rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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

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

Title:
  Dual Monitor Freeze after changing Display Settings in ubuntu 12.04

Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I had 11.10 64bit, I upgraded to 12.04

  if I change the settings in the Display it will freeze .
  -  if I move the external monitor  to the left of laptop monitor , (or above 
it) it will freeze
   - if I try to turn of the laptop monitor ,so I only have my external monitor 
it will freeze again.

  the mouse wont move and I have to reset the computer by ALT PRINT K to
  come back to ubuntu

  dual monitor used to work fine in ubuntu 11.10 , is there any way to
  downgrade the Display program to the one in 11.10 ?

  WORKAROUND: Install packages from
  https://launchpad.net/~sarvatt/+archive/sru1/+build/3118994

  ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta
  Tags:  precise precise
  Uname: Linux 3.3.0-030300rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/992778/+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 1849484] ProcCpuinfo.txt

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]

[Jonathan Kamens]

FYI: While apport-collect was running, my screens went blank briefly and
then when they came back my monitor configuration was wrong: the ultra-
wide monitor was at a lower resolution than it's supposed to be and the
two monitors' relative positions were not configured correctly.
Unplugging the ultra-wide and plugging it back in fixed this situation.
This is similar to the behavior I see which prompted me to file this bug
in the first place. It would seem that something that apport-collect did
triggers the issue or a similar one.

So does launching the TeamViewer client, by the way.

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  

[Kernel-packages] [Bug 1849484] xdpyinfo.txt

[Jonathan Kamens]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300918/+files/xdpyinfo.txt

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

** 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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: 

[Kernel-packages] [Bug 1849484] Xrandr.txt

[Jonathan Kamens]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1849484/+attachment/5300917/+files/Xrandr.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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] XorgLogOld.txt

[Jonathan Kamens]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300916/+files/XorgLogOld.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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] XorgLog.txt

[Jonathan Kamens]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300915/+files/XorgLog.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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1849484/+attachment/5300911/+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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] UnitySupportTest.txt

[Jonathan Kamens]

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300913/+files/UnitySupportTest.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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] MonitorsUser.xml.txt

[Jonathan Kamens]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300904/+files/MonitorsUser.xml.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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] DpkgLog.txt

[Jonathan Kamens]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300900/+files/DpkgLog.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/1849484

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Kernel-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]

[Jonathan Kamens]

apport information

** Tags added: apport-collected ubuntu

** Description changed:

  I have an LG ultra-wide (2560x1080) monitor.
  
  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else happens.
  I can still see the mouse cursor and move it between the two monitors
  (sometimes in the correct location configuration I've configured,
  sometimes not), but nothing is rendered on the screens.
  
  Sometimes when I plug the monitor in, it comes on, but the resolution is
  wrong.
  
  Sometimes it is actually recognized and configured correctly.
  
  Frequently I have to unplug the monitor and plug it back in three times
  or more before it is recognized correctly.
  
  I wish it just worked right the first time. :-/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
+ --- 
+ ProblemType: Bug
+ .tmp.unity_support_test.0:
+  
+ ApportVersion: 2.20.11-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  jik3196 F pulseaudio
+  /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
+  /dev/snd/controlC0:  jik3196 F pulseaudio
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
+ DistroCodename: eoan
+ DistroRelease: Ubuntu 19.10
+ DistroVariant: ubuntu
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
+Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
+ InstallationDate: Installed on 2019-09-12 (45 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ MachineType: LENOVO 20QD001VUS
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: xorg-server (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-19-generic N/A
+  linux-backports-modules-5.3.0-19-generic  N/A
+  linux-firmware1.183.1
+ Tags:  eoan ubuntu
+ Uname: Linux 5.3.0-19-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 07/04/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2HET30W (1.13 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20QD001VUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad X1 Carbon 7th
+ dmi.product.name: 20QD001VUS
+ dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
+ dmi.product.version: ThinkPad X1 Carbon 7th
+ dmi.sys.vendor: LENOVO
+ modified.conffile..etc.apport.crashdb.conf: [modified]
+ mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
+ version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
+ version.libdrm2: libdrm2 2.4.99-1ubuntu1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
+ version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
+ version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1849484/+attachment/5300897/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to 

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

[Jonathan Kamens]

apport information

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

Title:
  [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when
  plugged in only intermittently [Xorg only]

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have an LG ultra-wide (2560x1080) monitor.

  Sometimes when I plug it into my laptop, whose screen was working fine
  before I plugged it in, both screens go black but nothing else
  happens. I can still see the mouse cursor and move it between the two
  monitors (sometimes in the correct location configuration I've
  configured, sometimes not), but nothing is rendered on the screens.

  Sometimes when I plug the monitor in, it comes on, but the resolution
  is wrong.

  Sometimes it is actually recognized and configured correctly.

  Frequently I have to unplug the monitor and plug it back in three
  times or more before it is recognized correctly.

  I wish it just worked right the first time. :-/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 08:34:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (40 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago)
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jik3196 F pulseaudio
   /dev/snd/pcmC1D0p:   jik3196 F...m pulseaudio
   /dev/snd/controlC0:  jik3196 F pulseaudio
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-09-12 (45 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: 

[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Proposed
- phase-changed: Sunday, 27. October 2019 20:11 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
-   promote-to-proposed: Stalled -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
-   bionic/linux/pc-kernel: bug 1849852, bug 1849005
-   bionic/linux/pc-lowlatency-kernel: bug 1849853, bug 1849006
+   bionic/linux/pc-kernel: bug 1849005, bug 1849852
+   bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
-   xenial/linux-hwe: bug 1849854, bug 1849034
+   xenial/linux-hwe: bug 1849854
  variant: debs

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  bionic/linux: 4.15.0-68.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Monday, 28. October 2019 14:26 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  trackers:
bionic/linux-aws: bug 1849016
bionic/linux-fips: bug 1849023
bionic/linux-gke-4.15: bug 1849018
bionic/linux-ibm-gt: bug 1849020
bionic/linux-kvm: bug 1849019
bionic/linux-oem: bug 1849012
bionic/linux-oracle: bug 1849022
bionic/linux-raspi2: bug 1849008
bionic/linux-snapdragon: bug 1849011
bionic/linux/pc-kernel: bug 1849005, bug 1849852
bionic/linux/pc-lowlatency-kernel: bug 1849006, bug 1849853
xenial/linux-azure: bug 1849027
xenial/linux-gcp: bug 1849031
xenial/linux-hwe: bug 1849854
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850157] Re: nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed to build

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed
  to build

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Just upgraded to 19.10 and rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-kernel-source-418 (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 5.3.0-19-generic
  Date: Sat Oct 26 07:05:11 2019
  DuplicateSignature: 
dkms:nvidia-kernel-source-418:418.56-0ubuntu1:/var/lib/dkms/nvidia/418.56/build/common/inc/nv-linux.h:733:21:
 error: void value not ignored as it ought to be
  InstallationDate: Installed on 2019-08-08 (80 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageVersion: 418.56-0ubuntu1
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-418
  Title: nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed 
to build
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1850157/+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 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines

[Seth Forshee]

** Tags added: block-proposed

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

Title:
  update firmware for sound sof driver to fix the hang issue on several
  Dell machines

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  We expect this firmware update could be released with 19.10

  [Impact]
  We have a couple of Dell machines, after installing the system, it
  will hang randomly, and this issue was reported by factory, they met
  this issue a couple of times. Then we tried to reproduce this issue,
  finally reproduced it.

  [Fix]
  Intel debugged this issue as well, and they provided 4 kernel patches
  and a new firmware, we tested them, they really can fix the issue.
  And the patches were sent the SRU already, now it is time to update
  firmware.

  [Test Case]
  Install the system repeatedly and there is no hang issue anymore.

  [Regression Risk]
  Low, Intel told us there is no ABI change for the firmware, so
  it is safe to run this firmware both with the old driver (not applied
  those 4 patches) and the new driver (applied those 4 patches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1847250/+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 1850157] [NEW] nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed to build

[Victor Quinn]

Public bug reported:

Just upgraded to 19.10 and rebooted

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: nvidia-kernel-source-418 (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 5.3.0-19-generic
Date: Sat Oct 26 07:05:11 2019
DuplicateSignature: 
dkms:nvidia-kernel-source-418:418.56-0ubuntu1:/var/lib/dkms/nvidia/418.56/build/common/inc/nv-linux.h:733:21:
 error: void value not ignored as it ought to be
InstallationDate: Installed on 2019-08-08 (80 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageVersion: 418.56-0ubuntu1
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: nvidia-graphics-drivers-418
Title: nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed to 
build
UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)

** Affects: nvidia-graphics-drivers-418 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package eoan

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

Title:
  nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed
  to build

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Just upgraded to 19.10 and rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-kernel-source-418 (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 5.3.0-19-generic
  Date: Sat Oct 26 07:05:11 2019
  DuplicateSignature: 
dkms:nvidia-kernel-source-418:418.56-0ubuntu1:/var/lib/dkms/nvidia/418.56/build/common/inc/nv-linux.h:733:21:
 error: void value not ignored as it ought to be
  InstallationDate: Installed on 2019-08-08 (80 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageVersion: 418.56-0ubuntu1
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-418
  Title: nvidia-kernel-source-418 418.56-0ubuntu1: nvidia kernel module failed 
to build
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1850157/+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 1841841] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1841841

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

Title:
  disk stress test extremely slow progress after cpu offline/online

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  One of the test systems we use for testing snap updates is:
  Dell Inspiron 5759
  Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916

  We picked this one, some time ago from a pool of hardware to use for
  one of the test systems to test amd64/i386 snaps in beta.  One of the
  tests in the test suite does some disk stress testing using:

 bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

  Looking back through our results, I see that it has often taken from
  20-40 min. to complete the test, and sometimes hit our timeout
  threshold. More recently, it seems to always just timeout, but as far
  back as our history goes with testing on this platform, it's always
  seemed bad to some extent.  I tried the exact same test on another
  similar system, and it completed in only 11min. so we suspected a bad
  disk.  After replacing the disk with a new one, it still has the same
  problem.

  We only see this problem on the core18 i386 images though, not on
  core16, and not on core18-amd64.

  Looking into it some more, I discovered that it was easily reproducible 
outside the test suite, but *only* if I tried running it after the full test 
suite without rebooting.  If I reboot the system, and run the bonnie++ command 
above without the rest of the tests, it completes in about 13 min.
  I divided up the other tests and narrowed it down to a cpu offlining test - 
when that test runs, followed by this disk stress test, that's when it gets so 
horribly slow.

  This was all done using checkbox-snappy as the test suite, but if you
  have another way to get bonnie++ on here, it can be reproduced without
  it (or you can use bonnie++ from checkbox-snappy easily by doing 'sudo
  /snap/bin/checkbox-snappy.shell')

  Here's the basic instructions to reproduce (on core18-i386):
  $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu1/online"
  $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu2/online"
  $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu3/online"
  $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu1/online"
  $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu2/online"
  $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu3/online"
  $ sudo /snap/bin/checkbox-snappy.shell
  # bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

  Nothing particularly interesting in dmesg during all of this other than the 
NOHZ messages during cpu offline:
  [  189.085026] smpboot: CPU 1 is now offline
  [  199.371529] smpboot: CPU 2 is now offline
  [  203.291835] NOHZ: local_softirq_pending 282
  [  203.293167] NOHZ: local_softirq_pending 282
  [  203.294581] smpboot: CPU 3 is now offline
  [  247.521569] x86: Booting SMP configuration:
  [  247.521576] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  247.522892] Initializing CPU#1
  [  252.127965] smpboot: Booting Node 0 Processor 2 APIC 0x1
  [  252.129533] Initializing CPU#2
  [  255.632004] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  255.633565] Initializing CPU#3

  
  History I have for the past few kernels:
  4.15.0-52.56-226 - passed - 41m
  4.15.0-54.58-241 - passed - 36m
  4.15.0-55.60-246 - passed after some timeouts/retries, took 41m though
  4.15.0-55.60-253 - passed in 20min
  4.15.0-56.62-263 - fails - seems to take much much longer from this point on

  *These results were from that test as part of the full test run,
  including the cpu offlining test. When the test is run by itself on
  the same system, it takes only around 13min

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841841/+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 1841841] Re: disk stress test extremely slow progress after cpu offline/online

[Paul Larson]

reopening. I know it was automatically marked incomplete but there's no
apport on core18. I believe I've already included the relevant
information but I'm happy to provide more, or even get someone access to
this system.

** Changed in: linux (Ubuntu)
   Status: Expired => 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/1841841

Title:
  disk stress test extremely slow progress after cpu offline/online

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  One of the test systems we use for testing snap updates is:
  Dell Inspiron 5759
  Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916

  We picked this one, some time ago from a pool of hardware to use for
  one of the test systems to test amd64/i386 snaps in beta.  One of the
  tests in the test suite does some disk stress testing using:

 bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

  Looking back through our results, I see that it has often taken from
  20-40 min. to complete the test, and sometimes hit our timeout
  threshold. More recently, it seems to always just timeout, but as far
  back as our history goes with testing on this platform, it's always
  seemed bad to some extent.  I tried the exact same test on another
  similar system, and it completed in only 11min. so we suspected a bad
  disk.  After replacing the disk with a new one, it still has the same
  problem.

  We only see this problem on the core18 i386 images though, not on
  core16, and not on core18-amd64.

  Looking into it some more, I discovered that it was easily reproducible 
outside the test suite, but *only* if I tried running it after the full test 
suite without rebooting.  If I reboot the system, and run the bonnie++ command 
above without the rest of the tests, it completes in about 13 min.
  I divided up the other tests and narrowed it down to a cpu offlining test - 
when that test runs, followed by this disk stress test, that's when it gets so 
horribly slow.

  This was all done using checkbox-snappy as the test suite, but if you
  have another way to get bonnie++ on here, it can be reproduced without
  it (or you can use bonnie++ from checkbox-snappy easily by doing 'sudo
  /snap/bin/checkbox-snappy.shell')

  Here's the basic instructions to reproduce (on core18-i386):
  $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu1/online"
  $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu2/online"
  $ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu3/online"
  $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu1/online"
  $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu2/online"
  $ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu3/online"
  $ sudo /snap/bin/checkbox-snappy.shell
  # bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

  Nothing particularly interesting in dmesg during all of this other than the 
NOHZ messages during cpu offline:
  [  189.085026] smpboot: CPU 1 is now offline
  [  199.371529] smpboot: CPU 2 is now offline
  [  203.291835] NOHZ: local_softirq_pending 282
  [  203.293167] NOHZ: local_softirq_pending 282
  [  203.294581] smpboot: CPU 3 is now offline
  [  247.521569] x86: Booting SMP configuration:
  [  247.521576] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  247.522892] Initializing CPU#1
  [  252.127965] smpboot: Booting Node 0 Processor 2 APIC 0x1
  [  252.129533] Initializing CPU#2
  [  255.632004] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  255.633565] Initializing CPU#3

  
  History I have for the past few kernels:
  4.15.0-52.56-226 - passed - 41m
  4.15.0-54.58-241 - passed - 36m
  4.15.0-55.60-246 - passed after some timeouts/retries, took 41m though
  4.15.0-55.60-253 - passed in 20min
  4.15.0-56.62-263 - fails - seems to take much much longer from this point on

  *These results were from that test as part of the full test run,
  including the cpu offlining test. When the test is run by itself on
  the same system, it takes only around 13min

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841841/+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: i915: Display flickers during "flickerfree" boot (BIOS logo on a black background)

[Sebastien Bacher]

Daniel, do you still see the 'fb0: switching to inteldrmfb from EFI
VGA'? The kernel change is needed from what upstream said even if it
might not be enoguh for your problem so I think it should still be a
step in the right direction and we should enable the option

-- 
You 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:
  i915: Display flickers during "flickerfree" boot (BIOS logo on a black
  background)

Status in linux 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/ubuntu/+source/linux/+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 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375

[Agustin-ferrario]

Booted without problems in Disco

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

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

Title:
  Ubuntu won't boot on Dell Inspiron 7375

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, 
with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 
(videos of each unsuccessful boot will be attached).
  I was able to boot using a workaround, by adding to the kernel line:

  amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

  You can see it here:
  https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on-
  dell-inspiron-7375

  I used this workaround to run the apport-bug tool.

  The problem should be in an ubuntu specific vendor patch or configuration 
since I was able to boot successfully in:
  * CentOS 7 (kernel 3.10)
  * OpenSUSE Leap 15.1 (kernel 4.12.14)
  * OpenSUSE tumbleweed (kernel 5.1.16)
  * Fedora 30 (kernel 5.0.9)
  * Manjaro (kernel 4.19)
  * SystemRescueCd (kernel 4.19.34)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2186 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2186 F pulseaudio
  CasperVersion: 1.411
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 23 21:14:36 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=00:00.2 ---
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0GTNWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837688/+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