[Kernel-packages] [Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Oleh Dmytrychenko]

Tested with latest mainline kernel and gnome is failing to start with
similar issue.

kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled 
seq=1, emitted seq=3
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 2210 thread gnome-shel:cs0 pid 2239
kernel: [drm] GPU recovery disabled.

** Attachment added: "syslog-5.3-rc4.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+attachment/5282123/+files/syslog-5.3-rc4.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/1839758

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since kernel 5.0 rolled out through HWE last week my system is
  consistently locking up upon launch of Steam or 3D applications in
  WINE.

  Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/

  Worked around by using pre-update 4.18 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 15:47:27 2019
  DistUpgraded: 2018-03-26 22:50:10,989 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: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  InstallationDate: Installed on 2018-03-26 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago)
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming K7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se3
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming K7
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+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 1837788] Re: bcache kernel warning when attaching device

[Khaled El Mously]

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

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

Title:
  bcache kernel warning when attaching device

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

   * Users can get a Warning or even Oops the kernel if
 bcache/writeback_percent is set before attaching a
 caching device to the bcache device.

   * The fix is trivial, upstream, and consists of just
 checking whether the caching device is attached in
 order to set flags and schedule thread (which oops).

  [Test Case]

   * See attachment 'setup-bcache-wb_percent-before-attach.sh'
 used in comment #5 and #6 to reproduce the problem(s).

   * for 'Warning':

 # make-bcache -B 
 # make-bcache -C 
 # echo 11 > /sys/block//bcache/writeback_percent
 # sleep 1
 # echo  > /sys/block//bcache/attach

   * for 'Oops':
 (steps above, but don't run last command / 'attach').

  [Regression Potential]

   * Low. The fix is trivial, contained, and exclusive to bcache sysfs
  handler.

   * The modified path has been exercised with synthetic testing
  (script).

  [Original Bug Description]

  See attached dmesg, each time this server is rebooted it emits a
  concerning bcache warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-54-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jul 24 12:28:06 2019
  InstallationDate: Installed on 2013-10-04 (2119 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Beta amd64 
(20130925.1)
  MachineType: Supermicro X9DAi
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic 
root=UUID=8577302d-1f37-40a6-afcd-385beb26059f ro nomodeset elevator=deadline 
nvme_core.default_ps_max_latency_us=0 nopti noibrs noibpb
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.9
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-09 (409 days ago)
  dmi.bios.date: 05/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DAi
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd05/09/2015:svnSupermicro:pnX9DAi:pvr0123456789:rvnSupermicro:rnX9DAi:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DAi
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837788/+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 1813463] Re: no bluetooth intel ac 9260

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  no bluetooth intel ac 9260

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi All

  Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 
5.0.
  Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

  hciconfig -a
  Produces no result

  $ bluetoothctl
  Agent registered
  [bluetooth]# show
  No default controller available
  [bluetooth]# devices
  No default controller available
  [bluetooth]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813463/+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 1804183] Re: netronome firmware symlinks are overwritten by package upgrade

[Launchpad Bug Tracker]

[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  netronome firmware symlinks are overwritten by package upgrade

Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  The linux-firmware package includes symlinks to installed Netronome
  firmware files. These links may be updated by a user but are
  overwritten when the linux-firmware package is upgraded whereas the
  desired behaviour is to leave existing symlinks unmodified.

  # apt install linux-firmware 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
linux-firmware
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 278 MB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.1 [64.6 MB]
  Fetched 64.6 MB in 1s (43.8 MB/s) 
  Selecting previously unselected package linux-firmware.
  (Reading database ... 59988 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.1_all.deb ...
  Unpacking linux-firmware (1.173.1) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  # cd /lib/firmware/netronome/
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_1x40.nffw -> 
nic/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_4x10.nffw -> 
nic/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0096-0001_2x10.nffw -> 
nic/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_2x40.nffw -> 
nic/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0097-0001_4x10_1x40.nffw -> 
nic/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_8x10.nffw -> 
nic/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x10.nffw -> 
nic/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x25.nffw -> 
nic/nic_AMDA0099-0001_2x25.nffw
  # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> 
flower/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> 
flower/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> 
flower/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> 
flower/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> 
flower/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> 
flower/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> 
flower/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> 
flower/nic_AMDA0099-0001_2x25.nffw
  # apt update
  ...
  # apt install linux-firmware
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following packages will be upgraded:
linux-firmware
  1 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 30.7 kB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.2 [64.6 MB]
  Fetched 64.6 MB in 1s (55.1 MB/s) 
  (Reading database ... 61821 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.2_all.deb ...
  Unpacking linux-firmware (1.173.2) over (1.173.1) ...
  Setting up linux-firmware (1.173.2) ...
  

[Kernel-packages] [Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  Expired
Status in lvm2 package in Ubuntu:
  Expired

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash 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-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+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 1832041] Re: The mouse stops working

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  The mouse stops working

Status in linux package in Ubuntu:
  Expired

Bug description:
  Sometime the wifi is not getting detected and the mouse is not working
  and and i am using touch instead of mouse, the external mouse is also
  not working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  8 00:40:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-47-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-51-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-17-generic, x86_64: installed
   nvidia, 390.116, 4.18.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba]
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 009: ID 03f0:0941 Hewlett-Packard 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 15-ch0xx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=a759c10c-be50-4caf-bd43-1516b97d1c6a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83BA
  dmi.board.vendor: HP
  dmi.board.version: 57.31
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.23:bd10/15/2018:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BA:rvr57.31:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-ch0xx
  dmi.product.sku: 2FW61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832041/+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 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

[Launchpad Bug Tracker]

[Expired for lvm2 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  Expired
Status in lvm2 package in Ubuntu:
  Expired

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash 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-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+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 1823725] Re: packet: reset network header if packet shorter than ll reserved space

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  packet: reset network header if packet shorter than ll reserved space

Status in linux package in Ubuntu:
  Expired

Bug description:
  After backport of linux upstream commit 9ed988cd5915 ("packet:
  validate variable length ll headers")
  (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
  missing :

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

  9ed988cd5915 ("packet: validate variable length ll headers")

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since kernel 5.0 rolled out through HWE last week my system is
  consistently locking up upon launch of Steam or 3D applications in
  WINE.

  Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/

  Worked around by using pre-update 4.18 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 15:47:27 2019
  DistUpgraded: 2018-03-26 22:50:10,989 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: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  InstallationDate: Installed on 2018-03-26 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago)
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming K7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se3
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming K7
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+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 1559391] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module failed to build [gcc: error: unrecognized command line option ‘-fstack-protector-strong’]

[Daniel van Vugt]

** Tags removed: wily
** Tags added: xenial

** Tags added: trusty

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module
  failed to build [gcc: error: unrecognized command line option
  ‘-fstack-protector-strong’]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 4.2.0-34-generic
  Date: Sat Mar 19 05:55:42 2016
  DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu7:gcc: 
error: unrecognized command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2015-08-27 (204 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1559391/+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 1839664] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build [gcc: error: unrecognized command line option ‘-fstack-protector-strong’]

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1559391, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module 
failed to build
+ bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module 
failed to build [gcc: error: unrecognized command line option 
‘-fstack-protector-strong’]

** This bug has been marked a duplicate of bug 1559391
   bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module failed 
to build [gcc: error: unrecognized command line option 
‘-fstack-protector-strong’]

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel
  module failed to build [gcc: error: unrecognized command line option
  ‘-fstack-protector-strong’]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  I have the following error when trying to upgrade from Ubuntu 14 to
  Ubuntu 16

  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.4.0-148-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-148-generic
  Date: Fri Aug  9 12:42:16 2019
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:gcc: error: 
unrecognized command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2019-05-10 (91 days ago)
  InstallationMedia: It
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.23
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel 
module failed to build
  UpgradeStatus: Upgraded to xenial on 2019-08-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1839664/+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 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

Status in linux package in Ubuntu:
  New

Bug description:
  Since kernel 5.0 rolled out through HWE last week my system is
  consistently locking up upon launch of Steam or 3D applications in
  WINE.

  Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/

  Worked around by using pre-update 4.18 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 15:47:27 2019
  DistUpgraded: 2018-03-26 22:50:10,989 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: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  InstallationDate: Installed on 2018-03-26 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago)
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming K7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se3
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming K7
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+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 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Daniel van Vugt]

** Summary changed:

- System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
+ [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 
5.0.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Tags added: regression-update

** Tags added: amdgpu

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

Status in linux package in Ubuntu:
  New

Bug description:
  Since kernel 5.0 rolled out through HWE last week my system is
  consistently locking up upon launch of Steam or 3D applications in
  WINE.

  Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/

  Worked around by using pre-update 4.18 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 15:47:27 2019
  DistUpgraded: 2018-03-26 22:50:10,989 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: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  InstallationDate: Installed on 2018-03-26 (502 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago)
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F25
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming K7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se3
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming K7
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Khaled El Mously]

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

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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

  derivatives: bug 1839259 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Monday, 12. August 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839259
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+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 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -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
  
  derivatives: bug 1839259 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Ready for Testing
- phase-changed: Friday, 09. August 2019 19:45 UTC
+ phase: Testing
+ phase-changed: Monday, 12. August 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839259
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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

  derivatives: bug 1839259 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Monday, 12. August 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839259
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+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 1839758] [NEW] [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Since kernel 5.0 rolled out through HWE last week my system is
consistently locking up upon launch of Steam or 3D applications in WINE.

Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/

Worked around by using pre-update 4.18 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 11 15:47:27 2019
DistUpgraded: 2018-03-26 22:50:10,989 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: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed
 virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
InstallationDate: Installed on 2018-03-26 (502 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago)
dmi.bios.date: 01/16/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F25
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming K7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: se3
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming K7
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze raven ridge ubuntu
-- 
[amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
https://bugs.launchpad.net/bugs/1839758
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 1839637] Re: Display driver missing

[Daniel van Vugt]

This sounds like a regression of bug 1727356. And it appears the patch
for that bug was dropped in mutter version:

  3.28.3+git20190124-0ubuntu18.04.1

because it was upstreamed and is in mutter version 3.28.4. And still is.

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

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

[Daniel van Vugt]

Please:

1. Switch out of recovery mode and boot normally so as to reproduce the
bug.

2. Reboot again into recovery mode and then run:

   journalctl -b-1 > preboot.txt

   and then attach the file 'prevboot.txt' here.

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

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -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
  
  derivatives: bug 1837596 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 07:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1837596
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1837596 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 07:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1837596
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837598/+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 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1837596 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 07:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1837596
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837598/+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 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1122.128/snapdragon-4.4-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1837596 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 07:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1837596
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837598/+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 1837638] Re: Add the EFA driver into linux-aws

[Khaled El Mously]

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

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

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

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

Title:
  Add the EFA driver into linux-aws

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

Bug description:
  [Impact]

  * The open source EFA driver belongs in the AWS kernels
  (https://github.com/amzn/amzn-drivers/tree/master/kernel/linux/efa)

  [Test Case]

   * Boot tested into each kernel. Loaded and unloaded the module.

  [Regression Potential]

  This is a new feature constrained to a custom kernel. Most of the
  patches have been reviewed and applied to mainline. The compatibility
  fixup sauce patch is big, but is all preprocessor directives for
  conditional compilation and these have been maintained in the Github
  repo during the driver's development. Basically, the blast radius of
  this pull request should be confined only to this new module and
  should not impact any other area of the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837638/+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 1839637] Re: [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied

[Daniel van Vugt]

Oh, it's not a bug. Your machine is just stuck in recovery mode:

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset


** Summary changed:

- [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied
+ Display driver missing

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

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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

  derivatives: bug 1839257 (pi-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Friday, 09. August 2019 19:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1839257
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+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 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.15.0-1043.46/raspi2-4.15-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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

  derivatives: bug 1839257 (pi-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Friday, 09. August 2019 19:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1839257
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+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 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -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
  
  derivatives: bug 1839257 (pi-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Friday, 09. August 2019 19:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1839257
  variant: debs

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

Title:
  bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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

  derivatives: bug 1839257 (pi-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Friday, 09. August 2019 19:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1839257
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+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 1839637] Re: Display driver missing

[Daniel van Vugt]

It appears you have an Intel CPU/GPU (Core 2 Duo E4500) and the Xorg
modesetting driver is failing to talk to the kernel driver properly:

[63.574] (EE) modeset(0): drmSetMaster failed: Permission denied


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Display driver missing
+ [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied

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

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

[Daniel van Vugt]

Can you please attach a photo or other evidence explaining how the
display driver is "missing"?

It's meant to be missing in recovery mode, so ignore that part.

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

** Changed in: xorg-server (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/1839637

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839637/+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 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -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
  
  derivatives: bug 1837592 (pi2-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1837592
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1837592 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1837592
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+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 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1837592 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1837592
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+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 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1118.127/raspi2-4.4-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1837592 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1837592
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+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 1839253] Re: Excessive screen tearing and flickering

[Daniel van Vugt]

If nothing gets added to the output when the flickering happens then
that answers my question, thanks.

This still feels like a kernel bug if not a hardware problem.

Do you notice any change if you wiggle the laptop screen? Try moving it
forward and backward. We next need to check if it's related to a loose
connection either in the screen or relating to the screen hinge.

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

Title:
  Excessive screen tearing and flickering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am experiencing a large amount of screen tearing flickering and
  artifacting. I've tried the common fix that is suggested on
  askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel-
  graphics.conf and this has not changed anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  7 02:06:01 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1]
  InstallationDate: Installed on 2019-08-06 (1 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 004: ID 27c6:5201  
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:56b9 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA
  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.0.0-23-generic 
root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839253/+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 1839253] Re: Excessive screen tearing and flickering

[Daniel van Vugt]

Also, did you verify that kernel 5.3 was running successfully?

  uname -a

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

Title:
  Excessive screen tearing and flickering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am experiencing a large amount of screen tearing flickering and
  artifacting. I've tried the common fix that is suggested on
  askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel-
  graphics.conf and this has not changed anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  7 02:06:01 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1]
  InstallationDate: Installed on 2019-08-06 (1 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 004: ID 27c6:5201  
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:56b9 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA
  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.0.0-23-generic 
root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839253/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it

[Daniel van Vugt]

** Summary changed:

- Bluetooth mouse sleeps after 5 seconds of inactivity
+ Bluetooth mouse sleeps after 5 seconds of inactivity, but 
btusb.enable_autosuspend=0 fixes it

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity, but
  btusb.enable_autosuspend=0 fixes it

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+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 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C

[Daniel van Vugt]

It's difficult because it seems only certain laptop models will be
affected very often. And while no developers are affected by the bug
then it's unlikely to get fixed. Because nobody with the ability to fix
the bug has the hardware to reproduce the bug.

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe A/B/C

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

Bug description:
  I have this error and arbitrary freezes on the system

  My System:

  Hardware:
  Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 
0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate 
ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: 
Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 
Gigabit + Intel Device a370

  Software:
  OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, 
Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, 
Screen Resolution: 1920x1980

  dmesg output:

  Dec  2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, 
min 894, max 899, scanline start 845, end 903
  Dec  2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup 
failure, AE_NOT_FOUND (20170831/psargs-364)
  Dec  2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized 
for Method [BRT6]
  Dec  2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method 
[BRT6]:  (2 arguments defined for method invocation)
  Dec  2 16:08:50 G5 kernel: [ 2534.448073]   Arg0:   a83faa08 
   Integer 0001
  Dec  2 16:08:50 G5 kernel: [ 2534.448076]   Arg1:   35246c42 
   Integer 
  Dec  2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution 
failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution 
failed \EV5, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution 
failed \SMEE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution 
failed \SMIE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution 
failed \NEVT, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution 
failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, 
min 894, max 899, scanline start 864, end 14
  Dec  2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b 
changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  instantcrush   1622 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G5 5587
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0M2MWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5587
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1839376] Re: Bionic update: upstream stable patchset 2019-08-07

[Khaled El Mously]

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

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

Title:
  Bionic update: upstream stable patchset 2019-08-07

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2019-08-07

     Ported from the following upstream stable releases:
     v4.14.137, v4.19.65

     from git://git.kernel.org/

  ARM: riscpc: fix DMA
  ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200
  ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again
  ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend
  ftrace: Enable trampoline when rec count returns back to one
  kernel/module.c: Only return -EEXIST for modules that have finished loading
  MIPS: lantiq: Fix bitfield masking
  dmaengine: rcar-dmac: Reject zero-length slave DMA requests
  clk: tegra210: fix PLLU and PLLU_OUT1
  fs/adfs: super: fix use-after-free bug
  btrfs: fix minimum number of chunk errors for DUP
  cifs: Fix a race condition with cifs_echo_request
  ceph: fix improper use of smp_mb__before_atomic()
  ceph: return -ERANGE if virtual xattr value didn't fit in buffer
  ACPI: blacklist: fix clang warning for unused DMI table
  scsi: zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized
  x86: kvm: avoid constant-conversion warning
  ACPI: fix false-positive -Wuninitialized warning
  be2net: Signal that the device cannot transmit during reconfiguration
  x86/apic: Silence -Wtype-limits compiler warnings
  x86: math-emu: Hide clang warnings for 16-bit overflow
  mm/cma.c: fail if fixed declaration can't be honored
  coda: add error handling for fget
  coda: fix build using bare-metal toolchain
  uapi linux/coda_psdev.h: move upc_req definition from uapi to kernel side 
headers
  drivers/rapidio/devices/rio_mport_cdev.c: NUL terminate some strings
  ipc/mqueue.c: only perform resource calculation if user valid
  xen/pv: Fix a boot up hang revealed by int3 self test
  x86/kvm: Don't call kvm_spurious_fault() from .fixup
  x86/paravirt: Fix callee-saved function ELF sizes
  x86, boot: Remove multiple copy of static function sanitize_boot_params()
  drm/nouveau: fix memory leak in nouveau_conn_reset()
  kbuild: initialize CLANG_FLAGS correctly in the top Makefile
  Btrfs: fix incremental send failure after deduplication
  Btrfs: fix race leading to fs corruption after transaction abort
  mmc: dw_mmc: Fix occasional hang after tuning on eMMC
  gpiolib: fix incorrect IRQ requesting of an active-low lineevent
  IB/hfi1: Fix Spectre v1 vulnerability
  selinux: fix memory leak in policydb_init()
  s390/dasd: fix endless loop after read unit address configuration
  parisc: Fix build of compressed kernel even with debug enabled
  drivers/perf: arm_pmu: Fix failure path in PM notifier
  nbd: replace kill_bdev() with __invalidate_device() again
  xen/swiotlb: fix condition for calling xen_destroy_contiguous_region()
  IB/mlx5: Fix unreg_umr to ignore the mkey state
  IB/mlx5: Use direct mkey destroy command upon UMR unreg failure
  IB/mlx5: Move MRs to a kernel PD when freeing them to the MR cache
  IB/mlx5: Fix RSS Toeplitz setup to be aligned with the HW specification
  IB/hfi1: Check for error on call to alloc_rsm_map_table
  eeprom: at24: make spd world-readable again
  objtool: Support GCC 9 cold subfunction naming scheme
  gcc-9: properly declare the {pv,hv}clock_page storage
  x86/vdso: Prevent segfaults due to hoisted vclock reads
  Documentation: Add swapgs description to the Spectre v1 documentation
  firmware/psci: psci_checker: Park kthreads before stopping them
  btrfs: qgroup: Don't hold qgroup_ioctl_lock in btrfs_qgroup_inherit()
  lib/test_string.c: avoid masking memset16/32/64 failures
  mmc: meson-mx-sdio: Fix misuse of GENMASK macro
  arm64: compat: Allow single-byte watchpoints on all addresses
  arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG}
  IB/mlx5: Fix clean_mr() to work in the expected order
  ARC: enable uboot support unconditionally
  scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
  UBUNTU: upstream stable to v4.14.137, v4.19.65

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post 

[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours

[Khaled El Mously]

** Changed in: linux-azure (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the
  VM was unavailable for 2 hours

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure source package in Disco:
  Fix Committed

Bug description:
  Can you please pick up the following 4 patches? They resolve this live
  migration that was reported by a mutual customer.

  PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary
  PCI: hv: Add hv_pci_remove_slots() when we unload the driver
  PCI: hv: Fix a memory leak in hv_eject_device_work()
  PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv

  
  This is a known issue in linux pci-hyperv driver and is fixed by these 
patches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+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 1579205] Re: CONFIG_NR_CPUS=256 is too low

[Po-Hsu Lin]

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

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

Title:
  CONFIG_NR_CPUS=256 is too low

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

Bug description:
  Intel Knights Landing systems boot up to 272 processor cores. The
  stock Ubuntu Linux kernel images leave processor cores above 256
  disabled:

  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
256/0xeb ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
257/0xef ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
258/0xf3 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
259/0xf7 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
260/0xfb ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
261/0xff ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
262/0x103 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
263/0x107 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
264/0x10b ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
265/0x10f ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
266/0x113 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
267/0x117 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
268/0x11b ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
269/0x11f ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
270/0x123 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
271/0x127 ignored.

  I'd request an increase in CONFIG_NR_CPUS to 512. This would match
  Debian's default setting. For comparison, RHEL/CentOS ship with 4096.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579205/+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 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32

[Po-Hsu Lin]

For those who would like to benefit from this fix, please:
1. For fonts in early boot stage:
  Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in
  /etc/default/grub and run "sudo update-grub" and reboot
2. For fonts after boot (not related to this fix, but you might
need this as well):
  Run "sudo dpkg-reconfigure console-setup" to choose a bigger
  font. (if you need a non-interactive solution, please check
  https://askubuntu.com/questions/1105052

Thanks

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

Title:
  [CONFIG] please enable highdpi font FONT_TER16x32

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

Bug description:
  == Justification ==
  The console font size on a high resolution screen is only suitable for
  eagles, although we can choose a bigger font by running:
sudo dpkg-reconfigure console-setup

  But that is not enough, the font size before video driver kicks in is
  still small. If we need to debug some early stage issues that will be a
  problem.

  
  == Fix ==
  ac8b6f14 (Fonts: New Terminus large console font)
  Config for this TER16x32 and the compiled-in fonts support needs to be
  enabled to keep engineers away from ophthalmologists.

  * Disco
It's already there. Just need to enable the configs.
  * Cosmic / Bionic
Patch can be cherry-picked.
  * Xenial
It needs an extra patch to make it a clean cherry-pick:
* 7bcae826 (lib/fonts/Kconfig: keep non-Sparc fonts listed together
  * Trusty
It needs two extra patches to make it a clean cherry-pick:
* fonts: Add 6x10 font (33ac9dba)
* lib/fonts/Kconfig: keep non-Sparc fonts listed together (7bcae826).
And a config entry for the 6x10 font.

  Commit "fonts: Add 6x10 font" is just adding a new font.
  Commit "lib/fonts/Kconfig: keep non-Sparc fonts listed together" is
  just a patch for context rearrangement.

  I think these two are safe to be pulled-in.

  
  == Test ==
  Test kernels: http://people.canonical.com/~phlin/kernel/lp-1819881-font/

  Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in
  /etc/default/grub, and follow these steps.

  * Disco
sudo update-grub; sudo reboot
  * Cosmic / Bionic
Add "GRUB_GFXPAYLOAD_LINUX=3840x2160" to /etc/default/grub
sudo update-grub; sudo reboot
  * Xenial
sudo update-grub; sudo reboot
  * Trusty
sudo update-grub; sudo reboot (I need the proprietary nvidia driver
to boot for my SUT - Dell Precision M3800)

  The font before the video driver kicks in will get bigger.

  == Regression potential ==
  Minimal, changes are limited to adding console fonts, turn on fonts
  related kernel configs.


  
  [CONFIG] please enable highdpi font FONT_TER16x32

  This is now available in v5.0

  config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+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 1820760] Re: Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2

[Po-Hsu Lin]

That's a good news, thank you for your patience.

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

Title:
  Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  I have just bought a new laptop from Teclast model F6 Pro. I have
  installed Ubuntu LTS 18.04.2 (kernel 4.18.0-16-generic).

  The Goodix touchpad of the laptop is not recognized by the kernel
  version used by Ubuntu LTS 18.04.2.

  That is my kernel error:

  [3.733842] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, 
using dummy regulator
  [3.738296] i2c_hid i2c-SYNA3602:00: unexpected HID descriptor bcdVersion 
(0x)

  The problem is known, it is described here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1526312

  A patch is available here:
  https://github.com/brotfessor/sipodev/blob/master/b/i2c-hid.c

  It looks like that patch entered in the mainline kernel since 4.20 (or
  4.19 I am not sure).

  It would be very helpful if that patch is added to Ubuntu 18.04.2 LTS
  4.18.0-16-generic kernel to help the users of Teclast laptops like me.

  On several Teclast laptops the touchpad is not supported on Unbuntu
  18.04.2 (for sure F6 pro and F7).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-16-generic 4.18.0-16.17~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 22:28:07 2019
  InstallationDate: Installed on 2019-03-15 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820760/+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 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors

[oh]

With amdgpu.dc=0 I get random mouse lag after moving my mouse quickly.
The cursor will just stop moving. I turned amdgpu.dc=1 and it went away.

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

Title:
  amdgpu.dc dual monitor issues when trying to sleep / power off the
  monitors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a problem with my dual monitor setup on an AMD RX 580: when I lock the 
screen and Gnome try to power off both monitors the following happens:
  1) the second monitor goes to sleep before the first one, this is normal and 
expected because the first monitor has a longer time to sleep
  2) after some seconds the second monitor turn on back again and prevents the 
first one to sleep at all
  3) gnome detects inactivity on the lock screen for some time and try to power 
off the monitors again
  4) step 1 all over again in an infinite loop

  When I login back from the lock screen the windows inside my Gnome
  session can sometimes be rearranged from one screen to the other.

  After discovering this behavior I tried to power off the monitors
  manually with `xset dpms force off` and I can confirm that the same
  happens: the monitors wont really power off because the second one
  turns back on and prevents the first one to sleep.

  My guess was that somehow when the second monitor was turning off it
  delivered some kind of "monitors changed, you should reset" message to
  the GPU which in order did some kind of "reset everything and power on
  the monitors back again" action.

  Searching for a fix to this problem I tried to upgrade my amdgpu mesa
  drivers using the oibaf/graphics-drivers ppa and after this I tried to
  upgrade my whole distribution too, moving from bionic to cosmic.

  Nothing worked.

  In the end I discovered the existence of amdgpu.dc and tried to
  disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did
  the trick but it is still a workaround.

  I'm not sure this is the right place to report this kind of issues but as the 
issue is somehow critical (the first I entered the power on/off loop I didn't 
notice it and my monitor cycled power for two hours) I hope this will help 
other people.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.17.0-9-generic.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,104385b0,00100302'
 Controls  : 50
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100700'
 Controls  : 42
 Simple ctrls  : 6
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2
  InstallationDate: Installed on 2018-09-01 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic
  Uname: Linux 4.17.0-9-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1836176] Re: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

[Andrej Friesen]

Trying to use the fix in arch wiki does not work:

```
sudo rtcwake -m freeze -s 1
rtcwake: wakeup from "freeze" using /dev/rtc0 at Sun Aug 11 22:42:06 2019


rtcwake: write error
```

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

Title:
  Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As described above. With the last BIOS-updates Lenovo enabled proper
  S3 deep sleep mode for Linux. Sadly the touchscreen doesn't work after
  resuming. There are a lot of others facing the same problem:

  https://forums.lenovo.com/t5/Other-Linux-Discussions/X1Y3-Touchscreen-
  not-working-after-resume-on-Linux/td-p/4021200/highlight/false

  A workaround described in the Arch-wiki doesn't seem to work on
  Ubuntu:
  
https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Yoga_(Gen_3)#Fix_touchscreen_after_resume

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  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.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   4186 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 11:19:05 2019
  HibernationDevice: RESUME=UUID=1c3b8070-c343-4dbf-8fe2-4112233d7954
  InstallationDate: Installed on 2018-11-30 (222 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20LES01W00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=d887a86a-3729-4962-9692-d9db9d49ed4c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-14 (87 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET49W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES01W00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET49W(1.35):bd06/12/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES01W00
  dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836176/+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 1836176] Re: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

[Andrej Friesen]

Also using this machine and tried the fix on the arch wiki.

I am using bios 1.35 and fedora 30:

uname -a
Linux x1-yoga 5.2.6-200.fc30.x86_64 #1 SMP Mon Aug 5 13:20:47 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

Can we do something to get better debugging information?

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

Title:
  Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As described above. With the last BIOS-updates Lenovo enabled proper
  S3 deep sleep mode for Linux. Sadly the touchscreen doesn't work after
  resuming. There are a lot of others facing the same problem:

  https://forums.lenovo.com/t5/Other-Linux-Discussions/X1Y3-Touchscreen-
  not-working-after-resume-on-Linux/td-p/4021200/highlight/false

  A workaround described in the Arch-wiki doesn't seem to work on
  Ubuntu:
  
https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Yoga_(Gen_3)#Fix_touchscreen_after_resume

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  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.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   4186 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 11 11:19:05 2019
  HibernationDevice: RESUME=UUID=1c3b8070-c343-4dbf-8fe2-4112233d7954
  InstallationDate: Installed on 2018-11-30 (222 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20LES01W00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=d887a86a-3729-4962-9692-d9db9d49ed4c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-14 (87 days ago)
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET49W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES01W00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET49W(1.35):bd06/12/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES01W00
  dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO

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

Title:
  MicroSD not mounted when inserted, used to work correctly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with
  an adaptor in my laptop's SD slot, but it was not mounted nor
  apparently detected. I'm certain that until few weeks ago it was
  working correctly, so I suppose the cause to be an update regression.

  I tested the same card on another laptop using Ubuntu 18.04 LTS and it
  works correctly. Also, I have tested another card (16GB) on the 19.10
  laptop, and it's detected and mounted correctly.

  Summary:
  - 16GB SD card, FAT32 - Works with all Ubuntu versions
  - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.

  I'd be happy to help debugging this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-10-generic 5.2.0-10.11
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fabio  2086 F pulseaudio
   /dev/snd/controlC0:  fabio  2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 19:50:53 2019
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2019-02-03 (188 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 006: ID 13d3:3408 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-10-generic N/A
   linux-backports-modules-5.2.0-10-generic  N/A
   linux-firmware1.181
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:51:12.078: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839773/+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 1839773] Re: MicroSD not mounted when inserted, used to work correctly

[fcole90]

I could now make it work, reinserting it again after removing it..

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

Title:
  MicroSD not mounted when inserted, used to work correctly

Status in linux package in Ubuntu:
  New

Bug description:
  Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with
  an adaptor in my laptop's SD slot, but it was not mounted nor
  apparently detected. I'm certain that until few weeks ago it was
  working correctly, so I suppose the cause to be an update regression.

  I tested the same card on another laptop using Ubuntu 18.04 LTS and it
  works correctly. Also, I have tested another card (16GB) on the 19.10
  laptop, and it's detected and mounted correctly.

  Summary:
  - 16GB SD card, FAT32 - Works with all Ubuntu versions
  - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.

  I'd be happy to help debugging this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-10-generic 5.2.0-10.11
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fabio  2086 F pulseaudio
   /dev/snd/controlC0:  fabio  2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 19:50:53 2019
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2019-02-03 (188 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 006: ID 13d3:3408 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-10-generic N/A
   linux-backports-modules-5.2.0-10-generic  N/A
   linux-firmware1.181
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:51:12.078: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839773/+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 1839773] Re: MicroSD not mounted when inserted, used to work correctly

[fcole90]

04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
Subsystem: ASUSTeK Computer Inc. RTL8411B PCI Express Card Reader 
[1043:202f]
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7815000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at f780 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [170] Latency Tolerance Reporting
Capabilities: [178] L1 PM Substates
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci

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

Title:
  MicroSD not mounted when inserted, used to work correctly

Status in linux package in Ubuntu:
  New

Bug description:
  Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with
  an adaptor in my laptop's SD slot, but it was not mounted nor
  apparently detected. I'm certain that until few weeks ago it was
  working correctly, so I suppose the cause to be an update regression.

  I tested the same card on another laptop using Ubuntu 18.04 LTS and it
  works correctly. Also, I have tested another card (16GB) on the 19.10
  laptop, and it's detected and mounted correctly.

  Summary:
  - 16GB SD card, FAT32 - Works with all Ubuntu versions
  - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.

  I'd be happy to help debugging this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-10-generic 5.2.0-10.11
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fabio  2086 F pulseaudio
   /dev/snd/controlC0:  fabio  2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 19:50:53 2019
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2019-02-03 (188 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 006: ID 13d3:3408 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-10-generic N/A
   linux-backports-modules-5.2.0-10-generic  N/A
   linux-firmware1.181
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:51:12.078: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839773/+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 1839773] [NEW] MicroSD not mounted when inserted, used to work correctly

[fcole90]

Public bug reported:

Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an
adaptor in my laptop's SD slot, but it was not mounted nor apparently
detected. I'm certain that until few weeks ago it was working correctly,
so I suppose the cause to be an update regression.

I tested the same card on another laptop using Ubuntu 18.04 LTS and it
works correctly. Also, I have tested another card (16GB) on the 19.10
laptop, and it's detected and mounted correctly.

Summary:
- 16GB SD card, FAT32 - Works with all Ubuntu versions
- 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.

I'd be happy to help debugging this issue.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-10-generic 5.2.0-10.11
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fabio  2086 F pulseaudio
 /dev/snd/controlC0:  fabio  2086 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 11 19:50:53 2019
GvfsMonitorError:
 This tool has been deprecated, use 'gio mount' instead.
 See 'gio help mount' for more info.
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2019-02-03 (188 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera
 Bus 001 Device 006: ID 13d3:3408 IMC Networks
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X550JK
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-10-generic N/A
 linux-backports-modules-5.2.0-10-generic  N/A
 linux-firmware1.181
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 19:51:12.078: The udisks-daemon is running (name-owner :1.10).
UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago)
dmi.bios.date: 10/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550JK.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550JK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550JK
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug eoan

** Description changed:

  Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an
  adaptor in my laptop's SD slot, but it was not mounted nor apparently
  detected. I'm certain that until few weeks ago it was working correctly,
  so I suppose the cause to be an update regression.
  
  I tested the same card on another laptop using Ubuntu 18.04 LTS and it
  works correctly. Also, I have tested another card (16GB) on the 19.10
  laptop, and it's detected and mounted correctly.
  
  Summary:
  - 16GB SD card, FAT32 - Works with all Ubuntu versions
- - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.04, at least 2 weeks ago was still working.
+ - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.
  
  I'd be happy to help debugging this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-10-generic 5.2.0-10.11
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  fabio  2086 F pulseaudio
-  /dev/snd/controlC0:  fabio  2086 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  fabio  2086 F pulseaudio
+  /dev/snd/controlC0:  fabio  2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 19:50:53 2019
  GvfsMonitorError:
-  This tool has been deprecated, use 'gio mount' instead.
-  See 'gio help mount' for more info.
+  This tool has been 

[Kernel-packages] [Bug 1839119] Re: xenial/linux: 4.4.0-159.187 -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
  
  backports: bug 1839115 (trusty/linux-aws), bug 1839117 
(trusty/linux-lts-xenial)
  derivatives: bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 
1839103 (pc-kernel), bug 1839107 (linux-aws), bug 1839110 (linux-kvm), bug 
1839155 (linux-fips)
  
  -- swm properties --
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 11:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1839115
trusty/linux-lts-xenial: bug 1839117
xenial/linux-aws: bug 1839107
xenial/linux-fips: bug 1839155
xenial/linux-kvm: bug 1839110
xenial/linux-raspi2: bug 1837594
xenial/linux-snapdragon: bug 1837598
xenial/linux/pc-kernel: bug 1839103
  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/1839119

Title:
  xenial/linux: 4.4.0-159.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: bug 1839115 (trusty/linux-aws), bug 1839117 
(trusty/linux-lts-xenial)
  derivatives: bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 
1839103 (pc-kernel), bug 1839107 (linux-aws), bug 1839110 (linux-kvm), bug 
1839155 (linux-fips)

  -- swm properties --
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 11:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1839115
trusty/linux-lts-xenial: bug 1839117
xenial/linux-aws: bug 1839107
xenial/linux-fips: bug 1839155
xenial/linux-kvm: bug 1839110
xenial/linux-raspi2: bug 1837594
xenial/linux-snapdragon: bug 1837598
xenial/linux/pc-kernel: bug 1839103
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839119/+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 1839119] Re: xenial/linux: 4.4.0-159.187 -proposed tracker

[Canonical Certification Team]

Kernel deb testing completes, no regressions found. Ready for Updates.
Results here: https://trello.com/c/PIZMZD8a/125-xenial-linux-
image-440-159-generic-440-159187

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Fix Released

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

Title:
  xenial/linux: 4.4.0-159.187 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: bug 1839115 (trusty/linux-aws), bug 1839117 
(trusty/linux-lts-xenial)
  derivatives: bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 
1839103 (pc-kernel), bug 1839107 (linux-aws), bug 1839110 (linux-kvm), bug 
1839155 (linux-fips)

  -- swm properties --
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 11:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1839115
trusty/linux-lts-xenial: bug 1839117
xenial/linux-aws: bug 1839107
xenial/linux-fips: bug 1839155
xenial/linux-kvm: bug 1839110
xenial/linux-raspi2: bug 1837594
xenial/linux-snapdragon: bug 1837598
xenial/linux/pc-kernel: bug 1839103
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839119/+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 1838886] Re: New ID in ums-realtek module breaks cardreader

[Uwe Schindler]

Hi,
I was able to try the 5.3.0 kernel from the PPA as stated above. It was a bit 
complicated, as I had to disable secure boot first, so it was good that I did 
not try it from remote (my wife would have killed me!).

In short: The problem persists. The ums-realtek driver does not work
with this device ID. Same kernel messages, 3 retries to find the phantom
device (sdb in my case) and always it gave up after timeout. After 3
tries the device is blocked completely.

This happened also after completely switching of system and
disconnecting from power coord.

In short: The device ID added in the latest commit to ums-realtek does
not work, so please revert it and also tell this upstream.

@Kai-Heng: When you committed that to upstream kernel, did you test this
on a real device? To me it's completely un-understandable why to
forcefully switch a device which works perfectly well with the default
USB storage driver to a custom vendor-specific driver without any
reason!

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

Title:
  New ID in ums-realtek module breaks cardreader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the
  Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly.

  Previously it accepted SD cards all the time. Now it looks like you
  have to insert the card on booting or shortly after booting to access
  it. If you wait longer, it no longer detects the card. The reason for
  this can be found in the kernel log (dmes). On boot it seems to detect
  a card in the reader, although there is none. After a while it says
  "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead
  device" and then resets the device. It tries this 3 times and then
  gives up completely. After that any real device plugged is no longer
  detected.

  The device is:  idVendor=0bda, idProduct=0153, bcdDevice=57.13

  Support for this was added in mainline kernel:
  
https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577

  And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE
  stack.

  Full log on boot (no card inserted):

  [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd
  [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [3.898319] usb 1-5.1: Product: USB2.0-CRW
  [3.898322] usb 1-5.1: Manufacturer: Generic
  [3.898324] usb 1-5.1: SerialNumber: 2012092657120
  [3.911571] usbcore: registered new interface driver usb-storage
  [3.914796] usbcore: registered new interface driver uas
  [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [3.924478] scsi host2: usb-storage 1-5.1:1.0
  [3.924649] usbcore: registered new interface driver ums-realtek
  [...]
  [   13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [   13.509592] scsi host2: usb-storage 1-5.1:1.0
  [   14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [   14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [   14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  170.961728] scsi 2:0:0:0: rejecting I/O to dead device
  [  170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  170.962073] scsi 2:0:0:0: [sdb] Sense not available.
  [  171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd
  [  172.194299] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [  172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  172.194327] usb 1-5.1: Product: USB2.0-CRW
  [  172.194338] usb 1-5.1: Manufacturer: Generic
  [  172.194346] usb 1-5.1: SerialNumber: 2012092657120
  [  172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [  172.212503] scsi host2: usb-storage 1-5.1:1.0
  [  173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [  173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [  173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  329.654468] usb 1-5.1: USB disconnect, device number 8
  [  329.665905] scsi 2:0:0:0: rejecting I/O to dead device
  [  329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  329.665976] scsi 2:0:0:0: [sdb] Sense not available.
  [  330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd
  [  330.910415] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [  330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  330.910444] usb 1-5.1: Product: 

[Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend

[Steven Mackenzie]

I tested with the latest mainline kernel, 5.2.8 (also with 5.2) and the
issue persists.

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

Title:
  [amdgpu] screen freeze after suspend

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

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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 1820760] Re: Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2

[Simone Pernice]

Yesterday my distribution updated to Ubuntu 18.04.3 and thanks to the
new kernel the touchpad is recognized and perfectly 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/1820760

Title:
  Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  I have just bought a new laptop from Teclast model F6 Pro. I have
  installed Ubuntu LTS 18.04.2 (kernel 4.18.0-16-generic).

  The Goodix touchpad of the laptop is not recognized by the kernel
  version used by Ubuntu LTS 18.04.2.

  That is my kernel error:

  [3.733842] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, 
using dummy regulator
  [3.738296] i2c_hid i2c-SYNA3602:00: unexpected HID descriptor bcdVersion 
(0x)

  The problem is known, it is described here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1526312

  A patch is available here:
  https://github.com/brotfessor/sipodev/blob/master/b/i2c-hid.c

  It looks like that patch entered in the mainline kernel since 4.20 (or
  4.19 I am not sure).

  It would be very helpful if that patch is added to Ubuntu 18.04.2 LTS
  4.18.0-16-generic kernel to help the users of Teclast laptops like me.

  On several Teclast laptops the touchpad is not supported on Unbuntu
  18.04.2 (for sure F6 pro and F7).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-16-generic 4.18.0-16.17~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 22:28:07 2019
  InstallationDate: Installed on 2019-03-15 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820760/+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 1833617] Re: [amdgpu] screen freeze after suspend

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-amdgpu (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/1833617

Title:
  [amdgpu] screen freeze after suspend

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

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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