[Kernel-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-440 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9

  ---

  I observed the following on Eoan as well with nvidia drivers older
  than 440.

  1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
  QXL + SPICE:

  
    
    
  
  
    
    
  

  2) When a host is booted with `prime-select intel` observing guest
  video output works fine with both virt-viewer (over SPICE) and remmina
  (over RDP);

  3) With `prime-select nvidia` Xorg crashes as described in
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 13 20:16:07 2020
  DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   nvidia, 440.59, 5.4.0-12-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1579009393
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755]
  InstallationDate: Installed on 2018-05-13 (641 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Razer Blade
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/dima
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ 
button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 4.02
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.sku: RZ09-01953E72
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Kernel-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9

  ---

  I observed the following on Eoan as well with nvidia drivers older
  than 440.

  1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
  QXL + SPICE:

  
    
    
  
  
    
    
  

  2) When a host is booted with `prime-select intel` observing guest
  video output works fine with both virt-viewer (over SPICE) and remmina
  (over RDP);

  3) With `prime-select nvidia` Xorg crashes as described in
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 13 20:16:07 2020
  DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   nvidia, 440.59, 5.4.0-12-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1579009393
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755]
  InstallationDate: Installed on 2018-05-13 (641 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Razer Blade
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/dima
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ 
button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 4.02
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.sku: RZ09-01953E72
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  

[Kernel-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9

  ---

  I observed the following on Eoan as well with nvidia drivers older
  than 440.

  1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
  QXL + SPICE:

  
    
    
  
  
    
    
  

  2) When a host is booted with `prime-select intel` observing guest
  video output works fine with both virt-viewer (over SPICE) and remmina
  (over RDP);

  3) With `prime-select nvidia` Xorg crashes as described in
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 13 20:16:07 2020
  DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   nvidia, 440.59, 5.4.0-12-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1579009393
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755]
  InstallationDate: Installed on 2018-05-13 (641 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Razer Blade
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/dima
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ 
button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 4.02
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.sku: RZ09-01953E72
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[gannon1]

@John Hoff Looks good to me. Can you try again after changing

[verb]
0x1a 0x707 0xc5

to

[verb]
0x1a 0x707 0x5

The latter should be identical to your hda-verb command (0x707 is the
encoding for SET_PIN_WIDGET_CONTROL) except that Early Patching modifies
the hda configuration BEFORE initializing the codec. I'm curious if that
makes it stick (ie continue working after you change sound sources or
stop the music).

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  

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

[Ubuntu Kernel Bot]

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

apport-collect 1891722

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

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

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

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

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

Title:
  Lenevo thinkbook touchpad is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using lenevo thinkbook. But its touchpad is not working in the
  ubuntu latest release.

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

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

[Kernel-packages] [Bug 1891722] [NEW] Lenevo thinkbook touchpad is not working

[Faisal Ibrahim]

Public bug reported:

I am using lenevo thinkbook. But its touchpad is not working in the
ubuntu latest release.

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


** Tags: touchpad

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1891722/+attachment/5401584/+files/devices

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

Title:
  Lenevo thinkbook touchpad is not working

Status in linux package in Ubuntu:
  New

Bug description:
  I am using lenevo thinkbook. But its touchpad is not working in the
  ubuntu latest release.

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

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

[Kernel-packages] [Bug 1890863] Re: [amdgpu] Display does not come on after suspend

[Nick]

1/2

** Attachment added: "prevboot5.8.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890863/+attachment/5401582/+files/prevboot5.8.txt

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

Title:
  [amdgpu] Display does not come on after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1890863/+subscriptions

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

[Kernel-packages] [Bug 1890863] Re: [amdgpu] Display does not come on after suspend

[Nick]

Thank you, attached log 1/2

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

Title:
  [amdgpu] Display does not come on after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1890863/+subscriptions

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

[Kernel-packages] [Bug 1890863] Re: [amdgpu] Display does not come on after suspend

[Nick]

2/2

** Attachment added: "prevboot5.8_2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890863/+attachment/5401583/+files/prevboot5.8_2.txt

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

Title:
  [amdgpu] Display does not come on after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/1890863/+subscriptions

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

[Kernel-packages] [Bug 1054458] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'

[Bill (franksmcb)]

This is occurring on Ubuntu MATE 20.10 daily with nvidia 390.138

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

Title:
  nvidia-detector crashed with ValueError in __get_value_from_name():
  invalid literal for int() with base 10: 'experimental-304'

Status in nvidia-common package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-common source package in Precise:
  Fix Released
Status in ubuntu-drivers-common source package in Precise:
  Invalid
Status in nvidia-common source package in Quantal:
  Invalid
Status in ubuntu-drivers-common source package in Quantal:
  Fix Released
Status in nvidia-common source package in Bionic:
  Invalid
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  If other people report this at the current level with xorg/nvidia it
  might be a bug. It is also possible the error stems from a bad
  combination of free and proprietary material. Further details will be
  provided as necessary/available.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: ubuntu-drivers-common 1:0.2.69
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Fri Sep 21 22:48:18 2012
  ExecutablePath: /usr/bin/nvidia-detector
  InterpreterPath: /usr/bin/python3.2mu
  ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   LANGUAGE=de_CH:de
  PythonArgs: ['/usr/bin/nvidia-detector']
  SourcePackage: ubuntu-drivers-common
  Title: nvidia-detector crashed with ValueError in __get_value_from_name(): 
invalid literal for int() with base 10: 'experimental-304'
  UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago)
  UserGroups: audio pulse pulse-access video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+subscriptions

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

[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

[Jeremy Nixon]

Ok I have found the trigger for the usb error on my system. I did not
have to insert/remove any device as such, but simply put the laptop into
suspend mode. At the moment it resumes from suspend, the error can be
consistently reproduced on both signed and testing kernels.

There are a number of other internal devices on the USB hub, such as
WebCam SC-10HDP12631N, and ELAN Touchscreen. See my attached kern.log
for full usb and suspend output.

Aug 14 18:05:57 730U3E kernel: [   95.978282] usb 1-1.5: reset full-speed USB 
device number 4 using ehci-pci
Aug 14 18:05:57 730U3E kernel: [   95.978287] usb 2-1.5: reset full-speed USB 
device number 3 using ehci-pci
Aug 14 18:05:57 730U3E kernel: [   95.978520] usb 3-3: reset high-speed USB 
device number 2 using xhci_hcd
Aug 14 18:05:57 730U3E kernel: [   96.166202] usb 1-1.4: reset high-speed USB 
device number 3 using ehci-pci
Aug 14 18:06:01 730U3E kernel: [  100.429382] usb usb4-port2: Cannot enable. 
Maybe the USB cable is bad?
Aug 14 18:06:05 730U3E kernel: [  104.520742] usb usb4-port2: Cannot enable. 
Maybe the USB cable is bad?
Aug 14 18:06:10 730U3E kernel: [  108.592236] usb usb4-port2: Cannot enable. 
Maybe the USB cable is bad?

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

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
  This bug was fixed by simply reverting the offending change. Bug 1859873 
tracks root causing the issue and reapplying the change w/ any necessary fixes.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  Kernel emits messages like:
  usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Seth Arnold]

I was reminded of this bug earlier today -- Andrea, Sultan, thanks so
much for fixing my issues. I've been happily running along for months
now. :) 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/1861359

Title:
  swap storms kills interactive use

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

Bug description:
  [Impact]

  The i915 shrinker can make the system unresponsive and kill
  interactive performance by swapping out dirty objects to reclaim more
  memory.

  [Test case]

  The problem can be easily reproduced running an I/O intensive writer,
  for example:

  $ dd if=/dev/zero of=/tmp/zero bs=1G count=32

  When the system is running out of memory and the i915 shrinker is
  called we can experience noticeable lags in the normal interactive
  activities (mouse not responding for 5-10 seconds, screen not
  refreshing, etc.).

  [Fix]

  Avoid the lags by preventing to swap out dirty objects in the i915
  shrinker (other cached objects can still be reclaimed).

  [Regression potential]

  The right fix would be to backport commit 2850748ef876 ("drm/i915:
  Pull i915_vma_pin under the vm->mutex"), available in v5.5+. However
  the backport is not trivial and the risk to introduce other bugs is
  high.

  A simple change like this (it's basically a one-liner that removes a
  flag) can be a reasonable compromise to prevent the problem and avoid
  the risk of introducing other bugs.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release

[Tom Ivar Johansen]

Thanks for your great work. I have just verified that the kernel works
as it should.

I don't know if I am supposed to add a tag as well or how to do it.


Again, thanks.

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

Title:
  Freezing on boot since kernel 4.15.0-72-generic release

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  In bug 1840239, HPET is disabled on some systems for they caused TSC
  being marked unstable while it is not. This caused an regression as bug
  1851216 that some systems may then hang at early, so a fix cherry picked
  back from v5.3-rc1. However, this fix also introduce yet another
  regression that some other users may hang at boot while PIT is diabled
  in the previous fix.

  [Fix]
  Commit 979923871f69 ("x86/timer: Don't skip PIT setup when APIC is
  disabled or in legacy mode") from v5.6-rc1, also backported to v5.4.19
  and v5.5.3, fixes PIT setup in this case.

  [Test Case]
  Simply boot a patch kernel on systems affected and it shouldn't hang.

  [Regression Potential]
  Low. Stable patch and trivial backport.

  [Other Info]
  The same fix for bug 1851216 was also backported to Disco and Eoan, but
  they were then fixed with this 979923871f69 commit backported in bug
  1866858 and bug 1867051, which pulls v5.4 stable patches into Disco and
  Eoan correspondingly, leaving B/OEM-B the only victims so far.

  == Original Bug Description ==

  After the update to install kernel 4.15.0-72-generic (a bit over a week ago) 
my computer will not boot. On boot, all I see is the purple screen with:
  Loading Linux 4.15.0-72-generic ...
  Loading initial ramdisk ...
  and nothing happens. Just sits there. I've waited about 5-10 minutes on 
occasion but to no avail.
  I've checked a number of logs in /var/log but not found anything.

  If I go into the advanced options and select kernel
  4.15.0-70-generic, the computer boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1977 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 21:53:14 2019
  HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
  InstallationDate: Installed on 2018-09-16 (454 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 04f2:b59e Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE Sabre 17WV8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Sabre 17WV8
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A:
  dmi.product.family: Sabre
  dmi.product.name: Sabre 17WV8
  dmi.product.version: Not Applicable
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: change DFLT_CCERROR counter name

[Frank Heimes]

** No longer affects: linux (Ubuntu Xenial)

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
 IBM z15.  This counter counts completed DEFLATE instructions
 with exit code 0, 1 or 2. Since exit code 0 means success
 and exit code 1 or 2 indicate errors, change the counter
 name to avoid confusion.  This counter is incremented each
 time the DEFLATE instruction completed regardless if an
 error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
 currently succeeds. After this patch has been applied the
 command does not work anymore. The file does not exist
 anymore. Use command 
 # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
 instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8

  Will be integrated into 20.10 by kernel 5.8 integration.

  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided

  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

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

[Kernel-packages] [Bug 1888507] Re: [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

[Thadeu Lima de Souza Cascardo]

Hi.

So, we clarified that some of the problems were not caused by the kernel
at all. The only thing missing is support to probe_read_kernel and
probe_read_user on 4.15 kernels. Is that needed for the offering?

If I didn't get it right, I am sorry. So, in order for us to meet your
expectations, I'll try to understand better what are the needs here:

1) Do you want support on 4.15 kernel on Ubuntu 18.04, right? Or is the
offering based on Ubuntu 20.04?

2) Do you expect to be able to use LLVM/clang 10? Or is LLVM/clang 8
sufficient for your needs? The bug has only been open for the linux
package, so we would need to get folks behind LLVM involved, or try to
fix this on the kernel somehow, which might delay things a little. Being
able to use LLVM/clang 8, it seems, would be a best fit to a short
deadline.

3) Building and running samples/bpf/ is not something we test. And
though it might help us catch regressions, I would suppose it's not a
requirement for the offering. If I am wrong in that supposition, are you
relying on the source package for something? Or is anything shipped in
binary packages incorrect (like that s930x typo) preventing things from
building correctly?

Right now, the best course we have, in case what you need is the probe
functions on 4.15 is to get this available on a kernel in -proposed in 3
weeks, and in -updates in 6 weeks. Would that work?

Thank you.
Cascardo.

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

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  We need to run BPF filters to analyse and monitor network traffic. The
  BPF filters are created by skydive (http://skydive.network). Currently
  skydive fails to install BPF filters on s390x (using Ubuntu 18.04
  currently, soon moving to Ubuntu 20.04).

  Because of these failures, we decided to try the BPF samples that come
  with the kernel first. These samples also fail on s390x while they
  work fine on Intel.

  shense@boe-build:~/bionic/samples/bpf$ uname -a
  Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 
2020 s390x s390x s390x GNU/Linux

  Example instructions:

  sudo apt install -y dpkg-dev clang llvm libelf-dev
  sudo apt-get source linux-image-unsigned-$(uname -r)
  cd linux-4.15.0/
  make headers_install
  make samples/bpf/

  Errors:

  shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map
  [sudo] password for shense:
  invalid relo for insn[4].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields

  
  shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test
  invalid relo for insn[22].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields

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

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

[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu9

---
pulseaudio (1:13.99.1-1ubuntu9) groovy; urgency=medium

  * d/p/0034-alsa-adjust-ucm-sink-source-priority-according-to-po.patch
  * d/p/0035-ucm-add-possibility-to-skip-the-UCM-card-completely-.patch
  * d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch
Make digital mic on the AMD Renoir machines work under gnome desktop
(LP: #1889217)

 -- Hui Wang   Sat, 08 Aug 2020 13:32:49 +0800

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

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  

[Kernel-packages] [Bug 1543919] Re: Remove EISA support from main kernel image and make it M (modular)

[Mikko Rantalainen]

Still warning messages emitted to kernel log each boot.

Ubuntu 20.04.1 LTS
5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux

I'm running over 10 year old systems and I don't need built-in support
for EISA. Does anybody even know anybody running old enough hardware to
require built-in support? Does anybody even know a use case where a
module wouldn't be enough?

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

Title:
  Remove EISA support from main kernel image and make it M (modular)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (This is a sort of RfC. )

  I have a PC that still has the good old PCI ports, but I am 100% sure that 
the active use of EISA dates back yet more 10 years.
  In other words, boards that _only_ support EISA date back 25 years now, while 
those that provide *one* EISA slot date back roughly 15 years (one of the 
Elitegroup K7 series comes to mind, from about 2001/02).

  So the EISA support *should* be provided, as we should even support ancient 
hardware (Linux principle :))
  However, why the EISA support is *compiled in* is beyond me.

  For instance, it creates lots of totally unnecessary noise in dmesg:

  [0.08] EISA bus registered
  [1.598316] platform eisa.0: Probing EISA bus 0
  [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1  
(repeated 10 times, i=i+1)
  [1.598368] platform eisa.0: EISA: Detected 0 cards

  For a 1997 mainboard, this would make perfect sense.
  But it is very probable that said mainboard would require linux-image-extra 
nonetheless to support some days-of-yore chipset.

  So why not leave it as a *module*, while removing its support from
  main kernel image once and for all?

  Your turn.

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

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

[Kernel-packages] [Bug 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels

[Jamie Strandboge]

FYI, John provided me a test kernel for 18.04 and it resolved the issue.
This will be the basis of the SRU.

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

Title:
  'ptrace trace' needed to readlink() /proc/*/ns/* files on older
  kernels

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

Bug description:
  Per 'man namespaces':

  "Permission to dereference or read (readlink(2)) these symbolic links is
  governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see
  ptrace(2)."

  This suggests that a 'ptrace read' rule should be sufficient to
  readlink() /proc/*/ns/*, which is the case with 5.4.0-42.46-generic
  (Ubuntu 20.04 LTS).

  However, on Ubuntu 18.04 LTS and 16.04 LTS, 'ptrace trace' is needed.
  Here is a reproducer:

  $ cat ./readlink-ns.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  void usage() {
fprintf(stderr, "Usage: readlink-ns -p  -n \n");
  }

  int main(int argc, char *argv[])
  {
pid_t pid = 0;
char *ns = NULL;
char path[PATH_MAX] = {};
char rpath[PATH_MAX] = {};
int c;

while ((c = getopt(argc, argv, "hn:p:")) != -1) {
switch(c) {
case 'n':
ns = optarg;
break;
case 'p':
pid = atoi(optarg);
break;
case 'h':
usage();
return 0;
case '?':
usage();
return 1;
default:
return 1;
}
}

int n = snprintf(path, sizeof(path), "/proc/%d/ns/%s", pid, ns);
if (n < 0 || (size_t)n >= sizeof(path)) {
fprintf(stderr, "cannot format string\n");
return 1;
}
path[n] = '\0';
printf("path:  %s\n", path);

n = readlink(path, rpath, sizeof(rpath));
if (n < 0) {
perror("readlink()");
return 1;
} else if (n == sizeof(rpath)) {
fprintf(stderr, "cannot readlink()\n");
return 1;
}
printf("rpath: %s\n", rpath);

return 0;
  }

  $ cat ./readlink-ns.apparmor
  #include 

  profile test {
#include 

# focal
ptrace (read) peer="unconfined",

# xenial, bionic
#ptrace (trace) peer="unconfined",
  }

  
  # bionic and xenial need 'ptrace trace'
  $ gcc ./readlink-ns.c && sudo apparmor_parser -r ./readlink-ns.apparmor && 
sudo aa-exec -p test -- ./a.out -p 1 -n pid
  path:  /proc/1/ns/pid
  readlink(): Permission denied

  Denial:
  Aug 07 14:40:59 sec-bionic-amd64 kernel: audit: type=1400 
audit(1596829259.675:872): apparmor="DENIED" operation="ptrace" profile="test" 
pid=1311 comm="a.out" requested_mask="trace" denied_mask="trace" 
peer="unconfined"

  
  # focal needs only 'ptrace read'
  $ gcc ./readlink-ns.c && sudo apparmor_parser -r ./readlink-ns.apparmor && 
sudo aa-exec -p test -- ./a.out -p 1 -n pid
  path:  /proc/1/ns/pid
  rpath: pid:[4026531836]

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

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

[Kernel-packages] [Bug 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM / B-GCP-5.4

[Po-Hsu Lin]

Also,
it has passed with all arches including zVM / LPAR on Focal 5.4.0-44.48 as well.

On Focal kernel config:
# CONFIG_RT_GROUP_SCHED is not set

Commit from Seth:
b7ac4514cc56ec
UBUNTU: [Config] Turn off CONFIG_RT_GROUP_SCHED everywhere

I think we can close this bug now.
Thanks

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

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

** Changed in: qa-regression-testing
   Status: New => Invalid

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

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM
  / B-GCP-5.4

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Issue found on zVM "kernel04" with 5.4.0-29.33

   ==
   FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
   Run kernel regression tests 
   --
   Traceback (most recent call last):
 File "./test-apparmor.py", line 1746, in test_regression_testsuite
   self.assertEqual(expected, rc, result + report)
   AssertionError: Got exit code 2, expected 0 
   
   running aa_exec
   
   running access
   xfail: ACCESS file rx (r)
   xfail: ACCESS file rwx (r)
   xfail: ACCESS file r (wx)
   xfail: ACCESS file rx (wx)
   xfail: ACCESS file rwx (wx)
   xfail: ACCESS dir rwx (r)
   xfail: ACCESS dir r (wx)
   xfail: ACCESS dir rx (wx)
   xfail: ACCESS dir rwx (wx)
   
   running at_secure
   
   running introspect
   
   running capabilities
   (ptrace)
   (sethostname)
   (setdomainname)
   (setpriority)
   (setscheduler)
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- 
unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set 
SCHED_RR: Operation not permitted'
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- all caps' 
was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation 
not permitted'
 preparing apparmor_2.13.3-7ubuntu5.dsc...  done
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- capability 
sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- all 
caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- 
capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't 
set SCHED_RR: Operation not permitted'
   (reboot)
   (chroot)
   (mlockall)
   (net_raw)

  Please find attachment for the complete test log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+subscriptions

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

[Kernel-packages] [Bug 1876697] Re: test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM / B-GCP-5.4

[Po-Hsu Lin]

Hello Thadeu,

ubuntu_qrt_apparmor test has passed on B-GCP-5.4 (5.4.0-1021.21~18.04.1)
and F-GCP 5.4.0-1016.16

Thanks.
Sam

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

Title:
  test_regression_testsuite from ubuntu_qrt_apparmor failed on Focal zVM
  / B-GCP-5.4

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Issue found on zVM "kernel04" with 5.4.0-29.33

   ==
   FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
   Run kernel regression tests 
   --
   Traceback (most recent call last):
 File "./test-apparmor.py", line 1746, in test_regression_testsuite
   self.assertEqual(expected, rc, result + report)
   AssertionError: Got exit code 2, expected 0 
   
   running aa_exec
   
   running access
   xfail: ACCESS file rx (r)
   xfail: ACCESS file rwx (r)
   xfail: ACCESS file r (wx)
   xfail: ACCESS file rx (wx)
   xfail: ACCESS file rwx (wx)
   xfail: ACCESS dir rwx (r)
   xfail: ACCESS dir r (wx)
   xfail: ACCESS dir rx (wx)
   xfail: ACCESS dir rwx (wx)
   
   running at_secure
   
   running introspect
   
   running capabilities
   (ptrace)
   (sethostname)
   (setdomainname)
   (setpriority)
   (setscheduler)
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- 
unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set 
SCHED_RR: Operation not permitted'
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- all caps' 
was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation 
not permitted'
 preparing apparmor_2.13.3-7ubuntu5.dsc...  done
   Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- capability 
sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- all 
caps' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: 
Operation not permitted'
   Error: changehat_wrapper failed. Test 'syscall_setscheduler changehat -- 
capability sys_nice' was expected to 'pass'. Reason for failure 'FAIL: Can't 
set SCHED_RR: Operation not permitted'
   (reboot)
   (chroot)
   (mlockall)
   (net_raw)

  Please find attachment for the complete test log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1876697/+subscriptions

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

[Kernel-packages] [Bug 1866994] Re: Screen backlight control not working on Dell XPS 15 7590

[Po-Hsu Lin]

5.4.0-18 released, mark this as fix-released.

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

Title:
  Screen backlight control not working on Dell XPS 15 7590

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I tried running Ubuntu 20.04 (ISO downloaded on March 10th) on a Dell XPS 15 
7590 with the 4k LED display (*not* OLED). The screen backlight control keys 
seem to be registered but the brightness remain unchanged.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ghislain   1632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Dell Inc. XPS 15 7590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ghislain   1632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Dell Inc. XPS 15 7590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1881909] Re: Screen tearing with Nvidia Optimus

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/mutter/+bug/1881909/+subscriptions

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

[Kernel-packages] [Bug 1881909] Re: Screen tearing with Nvidia Optimus

[Mohammad Kazemi]

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/mutter/+bug/1881909/+subscriptions

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

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

[Tim McCune]

Comment #28 seems to offer some good insights about the best path
forward here, also supporting that this bug should be reopened.  Note
that with a Google Wifi router, there is no capability to reconfigure
the router to work around this issue, as the poster mentions.

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi 

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

[Tim McCune]

kernel: iwlwifi :02:00.0: Microcode SW error detected.  Restarting 
0x200.
 kernel: iwlwifi :02:00.0: Start IWL Error Log Dump:
 kernel: iwlwifi :02:00.0: Status: 0x0040, count: 6
 kernel: iwlwifi :02:00.0: Loaded firmware version: 36.79ff3ccf.0 
8265-36.ucode
 kernel: iwlwifi :02:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN   
 kernel: iwlwifi :02:00.0: 0x00800AB4 | trm_hw_status0
 kernel: iwlwifi :02:00.0: 0x | trm_hw_status1
 kernel: iwlwifi :02:00.0: 0x000248FC | branchlink2
 kernel: iwlwifi :02:00.0: 0x0003A872 | interruptlink1
 kernel: iwlwifi :02:00.0: 0x083A | interruptlink2
 kernel: iwlwifi :02:00.0: 0x | data1
 kernel: iwlwifi :02:00.0: 0x0080 | data2
 kernel: iwlwifi :02:00.0: 0x0783 | data3
 kernel: iwlwifi :02:00.0: 0x3A00ECBD | beacon time
 kernel: iwlwifi :02:00.0: 0xEE5E030C | tsf low
 kernel: iwlwifi :02:00.0: 0x0422 | tsf hi
 kernel: iwlwifi :02:00.0: 0x | time gp1
 kernel: iwlwifi :02:00.0: 0x08035370 | time gp2
 kernel: iwlwifi :02:00.0: 0x0001 | uCode revision type
 kernel: iwlwifi :02:00.0: 0x0024 | uCode version major
 kernel: iwlwifi :02:00.0: 0x79FF3CCF | uCode version minor
 kernel: iwlwifi :02:00.0: 0x0230 | hw version
 kernel: iwlwifi :02:00.0: 0x00489000 | board version
 kernel: iwlwifi :02:00.0: 0x0B1B001C | hcmd
 kernel: iwlwifi :02:00.0: 0x8002200E | isr0
 kernel: iwlwifi :02:00.0: 0x0080 | isr1
 kernel: iwlwifi :02:00.0: 0x0800180A | isr2
 kernel: iwlwifi :02:00.0: 0x004178C8 | isr3
 kernel: iwlwifi :02:00.0: 0x | isr4
 kernel: iwlwifi :02:00.0: 0x00B3019C | last cmd Id
 kernel: iwlwifi :02:00.0: 0x | wait_event
 kernel: iwlwifi :02:00.0: 0x0094 | l2p_control
 kernel: iwlwifi :02:00.0: 0x00010020 | l2p_duration
 kernel: iwlwifi :02:00.0: 0x000F | l2p_mhvalid
 kernel: iwlwifi :02:00.0: 0x0004 | l2p_addr_match
 kernel: iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel
 kernel: iwlwifi :02:00.0: 0x02052035 | timestamp
 kernel: iwlwifi :02:00.0: 0x0034E0F0 | flow_handler
 kernel: iwlwifi :02:00.0: 0x | ADVANCED_SYSASSERT
 kernel: iwlwifi :02:00.0: 0x | umac branchlink1
 kernel: iwlwifi :02:00.0: 0x | umac branchlink2
 kernel: iwlwifi :02:00.0: 0x | umac interruptlink1
 kernel: iwlwifi :02:00.0: 0x | umac interruptlink2
 kernel: iwlwifi :02:00.0: 0x | umac data1
 kernel: iwlwifi :02:00.0: 0x | umac data2
 kernel: iwlwifi :02:00.0: 0x | umac data3
 kernel: iwlwifi :02:00.0: 0x | umac major
 kernel: iwlwifi :02:00.0: 0x | umac minor
 kernel: iwlwifi :02:00.0: 0x | frame pointer
 kernel: iwlwifi :02:00.0: 0x | stack pointer
 kernel: iwlwifi :02:00.0: 0x | last host cmd
 kernel: iwlwifi :02:00.0: 0x | isr status reg
 kernel: iwlwifi :02:00.0: Fseq Registers:
 kernel: iwlwifi :02:00.0: 0x04A24B2F | FSEQ_ERROR_CODE
 kernel: iwlwifi :02:00.0: 0x4C1A2CA0 | FSEQ_TOP_INIT_VERSION
 kernel: iwlwifi :02:00.0: 0x9CC2CAA3 | FSEQ_CNVIO_INIT_VERSION
 kernel: iwlwifi :02:00.0: 0xA10B | FSEQ_OTP_VERSION
 kernel: iwlwifi :02:00.0: 0x2967E333 | FSEQ_TOP_CONTENT_VERSION
 kernel: iwlwifi :02:00.0: 0x3DDEC6F7 | FSEQ_ALIVE_TOKEN
 kernel: iwlwifi :02:00.0: 0xD9F95773 | FSEQ_CNVI_ID
 kernel: iwlwifi :02:00.0: 0x55AAB7A0 | FSEQ_CNVR_ID
 kernel: iwlwifi :02:00.0: 0x0010 | CNVI_AUX_MISC_CHIP
 kernel: iwlwifi :02:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP
 kernel: iwlwifi :02:00.0: 0x0BADCAFE | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
 kernel: iwlwifi :02:00.0: 0x0BADCAFE | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
 kernel: iwlwifi :02:00.0: Collecting data: trigger 2 fired.
 kernel: ieee80211 phy0: Hardware restart was requested
 kernel: iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM
 kernel: iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM
 kernel: iwlwifi :02:00.0: FW already configured (0) - re-configuring
 wpa_supplicant[916]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
 wpa_supplicant[916]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 
noise= txrate=866700

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the 

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

[Tim McCune]

Same here.  I don't think this bug has been fixed.  Can we please reopen
it?

Machine: ThinkPad Carbon X1 6th gen (same as in this issue's description)
Linux: 5.6.14-2
firmware-iwlwifi: 20200619-1

$ modinfo iwlwifi | grep 7260
firmware:   iwlwifi-7260-17.ucode

This issue is specifically occurring with a Google Wifi router.

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | 

[Kernel-packages] [Bug 1891451] Re: Add TGL+ SAGV display support

[Timo Aaltonen]

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

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

Title:
  Add TGL+ SAGV display support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  On platforms with UHD panel, massive drawing area updates may cause
  screen to flash as half-baked render buffers with black areas being
  renedered.

  [Fix]

  This turns out to be the lack of full support to Intel System Agent
  Geyserville (SAGV), which has been landed to kernel v5.8. The required
  fix resides in https://patchwork.freedesktop.org/series/75129/, which
  seems a rolling set that its early parts have been committed separatedly
  several times. This patchset also depends on
  https://patchwork.freedesktop.org/series/72301/, which attempts to make
  global state handling more standardized.

  [Test Case]

  1. Trigger massive rect updates, e.g. cat a lengthy file in xterm, dump
  kernel git history, etc.
  2. Observe if screen flashes with half black panes, sometimes black
  stripes, etc.

  [Regression Potential]
  Medium. This is to backport a new feature landed to kernel early this
  year, even there is no later fixes patch found so far, it could still
  introduce incompatibility to older kernels. So far it behaves on both
  UHD and other lower resolutions.

  == Original Bug Description ==

  On platforms with UHD panel, massive drawing area updates may cause
  screen to flash as half-baked render buffers with black areas being
  renedered.

  [Reproduce Steps]
  1. boot to GUI
  2. generate massive screen updates by `while true; do dmesg; done` or so

  [Results]
  Expected Result:
  Text output correctly rendered on xterm smoothly

  Actual Result:
  Screen flashes with black strides, etc.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1855 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X35
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enx00e04c6801fa  no wireless extensions.
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=00ec17d2-a1e3-4363-a67b-a7c380cc9189 ro drm.debug=0x1ff 
log_buf_len=32M
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  RfKill:

  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.9
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: 202007-28063
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.9:bd07/30/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891451/+subscriptions

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

[Kernel-packages] [Bug 1891647] Re: Groovy update: v5.8.1 upstream stable release

[Seth Forshee]

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

Title:
  Groovy update: v5.8.1 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Groovy:
  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:

     v5.8.1 upstream stable release
     from git://git.kernel.org/

  
  scsi: ufs: Fix and simplify setup_xfer_req variant operation
  USB: serial: qcserial: add EM7305 QDL product ID
  USB: iowarrior: fix up report size handling for some devices
  usb: xhci: define IDs for various ASMedia host controllers
  usb: xhci: Fix ASMedia ASM1142 DMA addressing
  Revert "ALSA: hda: call runtime_allow() for all hda controllers"
  ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops
  ALSA: hda/ca0132 - Add new quirk ID for Recon3D.
  ALSA: hda/ca0132 - Fix ZxR Headphone gain control get value.
  ALSA: hda/ca0132 - Fix AE-5 microphone selection commands.
  ALSA: seq: oss: Serialize ioctls
  staging: android: ashmem: Fix lockdep warning for write operation
  staging: rtl8712: handle firmware load failure
  Staging: rtl8188eu: rtw_mlme: Fix uninitialized variable authmode
  Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
  Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
  Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt()
  omapfb: dss: Fix max fclk divider for omap36xx
  binder: Prevent context manager from incrementing ref 0
  Smack: fix use-after-free in smk_write_relabel_self()
  scripts: add dummy report mode to add_namespace.cocci
  lkdtm/heap: Avoid edge and middle of slabs
  vgacon: Fix for missing check in scrollback handling
  mtd: properly check all write ioctls for permissions
  leds: wm831x-status: fix use-after-free on unbind
  leds: lm36274: fix use-after-free on unbind
  leds: da903x: fix use-after-free on unbind
  leds: lm3533: fix use-after-free on unbind
  leds: 88pm860x: fix use-after-free on unbind
  gpio: max77620: Fix missing release of interrupt
  xattr: break delegations in {set,remove}xattr
  Revert "powerpc/kasan: Fix shadow pages allocation failure"
  powerpc/kasan: Fix shadow pages allocation failure
  PCI: tegra: Revert tegra124 raw_violation_fixup
  ima: move APPRAISE_BOOTPARAM dependency on ARCH_POLICY to runtime
  random32: move the pseudo-random 32-bit definitions to prandom.h
  random: random.h should include archrandom.h, not the other way around
  arm64: kaslr: Use standard early random function
  Linux 5.8.1

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

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

[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[John Hoff]

@gannon1 Thanks for the reply.  Perhaps I am missing something because
it seems like it should work, but I have not had any luck with the
method described by ironincoder.  Just to be sure I did it again from
the start using the following steps (perhaps I just didn't understand
and missed a step)...

- I ran alsa_info.sh and found the relevant section :

 !!HDA-Intel Codec information
 !!---
 --startcollapse--

 Codec: Realtek ALC298
 Address: 0
 AFG Function Id: 0x1 (unsol 1)
 Vendor Id: 0x10ec0298
 Subsystem Id: 0x144dc18a
 Revision Id: 0x100103

- I created a new file named   /lib/firmware/alc298-sound-patch.fw
and included this text in that file (his comments said you could skip
the model section):

 [codec]
 0x10ec0298 0x144dc18a 0

 [verb]
 0x1a 0x707 0xc5

- I created a new file named/etc/modprobe.d/alc298-sound-patch.conf
and included this text :

 options snd-hda-intel 
patch=alc298-sound-patch.fw,alc298-sound-patch.fw,alc298-sound- 
 patch.fw,alc298-sound-patch.fw


- I rebooted completely and plugged in my headphones and turned on some music.  
I didn't hear anything.


- I then manually ran the commandsudo hda-verb /dev/snd/hwC0D0 0x1a 
SET_PIN_WIDGET_CONTROL 0x5
 and it works perfectly until I change sound sources or the music stops.


Did I miss a step to make this active?  I can share the full output of 
alsa_info.sh if its helpful...

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: 

[Kernel-packages] [Bug 1891652] Re: bcmwl-kernel-source fails to install on kernel 5.4.0-44-generic

[Scott Stensland]

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

** This bug has been marked a duplicate of bug 1878045
   doing dist-upgrade got error related do Broadcom

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

Title:
  bcmwl-kernel-source fails to install on kernel 5.4.0-44-generic

Status in bcmwl package in Ubuntu:
  New

Bug description:
  dell laptop wifi worked prior to upgrade from Ubuntu 20.04 to 20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55
  Uname: Linux 5.4.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 14 09:23:10 2020
  InstallationDate: Installed on 2020-04-23 (112 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: Upgraded to groovy on 2020-08-13 (0 days ago)

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

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

[Kernel-packages] [Bug 1891585] Re: alsa/sof: support 1 and 3 dmics

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

Title:
  alsa/sof: support 1 and 3 dmics

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-oem-5.6 package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Triaged
Status in linux-firmware source package in Focal:
  Triaged
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Triaged
Status in linux-firmware source package in Groovy:
  Triaged

Bug description:
  This is for linux-firmware:

  [Impact]
  On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
  it alwasys report 0 dmics on the machine. So users doesn't have
  internal mic to use.

  [Fix]
  Intel provides 2 new topology files to us, they could support 1
  dmic and 3 dmics.

  [Test Case]
  Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
  the linux-firmware, the sof driver could detect the dmic and users
  have a workable internal mic after booting up.

  [Regression Risk]
  This is adding 2 new topology files, not changing anything on
  current sof-firmware, so the regression posibility is very low.

  This is for linux kernel:

  [Impact]
  On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
  it alwasys report 0 dmics on the machine. So users doesn't have
  internal mic to use.

  [Fix]
  Intel write a patch to fix this issue, if NHLT table returns 1 or
  3 dmics, the sof driver will not fail like before, it can support
  1 or 3 dmics after applying this patch.

  [Test Case]
  Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
  the linux-firmware, the sof driver could detect the dmic and users
  have a workable internal mic after booting up.

  [Regression Risk]
  This patch adds new support for 1 and 3 dmics, it doesn't change
  anything on existing functions, so the regression posibility is very
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891585/+subscriptions

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

[Kernel-packages] [Bug 1891617] Re: Fix missing HDMI Audio on another HP Desktop

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Fix missing HDMI Audio on another HP Desktop

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  There's another HP desktop doesn't claim to support HDMI audio.

  [Fix]
  Add the system to HDMI force connect quirk list.

  [Test]
  With the patch applied, we can find HDMI codec under /proc/asound/card0
  and audio playback through HDMI works.

  [Regression Potential] 
  This fix doesn't bring any functional change other than the targeted
  platform. The platform in question is not on the market yet so the
  risk of regression is minimal.

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

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

[Kernel-packages] [Bug 1891652] [NEW] bcmwl-kernel-source fails to install on kernel 5.4.0-44-generic

[Scott Stensland]

Public bug reported:

dell laptop wifi worked prior to upgrade from Ubuntu 20.04 to 20.10

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55
Uname: Linux 5.4.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Aug 14 09:23:10 2020
InstallationDate: Installed on 2020-04-23 (112 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: bcmwl
UpgradeStatus: Upgraded to groovy on 2020-08-13 (0 days ago)

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


** Tags: amd64 apport-bug groovy third-party-packages

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

Title:
  bcmwl-kernel-source fails to install on kernel 5.4.0-44-generic

Status in bcmwl package in Ubuntu:
  New

Bug description:
  dell laptop wifi worked prior to upgrade from Ubuntu 20.04 to 20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55
  Uname: Linux 5.4.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 14 09:23:10 2020
  InstallationDate: Installed on 2020-04-23 (112 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: Upgraded to groovy on 2020-08-13 (0 days ago)

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

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

[Kernel-packages] [Bug 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels

[Marcelo Cerri]

Thanks for the detailed instructions, Dexuan. "ignore_loglevel
no_console_suspend" was the missing piece for me.

I'm still running tests but so far the results are good with the
reverted commit.

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

Title:
  [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels

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

Bug description:
  Microsoft would like to request commits to enable VM hibernation in
  the Azure 5.4 kernels for 18.04 and 20.04.

  Some of the commits needed to enable VM hibernation were included in
  mainline 5.4 and older.  However, 24 commits were added in 5.5 and
  later, which are required in the 5.4 kernel.  The list of commits
  requested are:

  38dce4195f0d  x86/hyperv: Properly suspend/resume reenlightenment 
notifications
  2351f8d295ed  PM: hibernate: Freeze kernel threads in software_resume()
  421f090c819d  x86/hyperv: Suspend/resume the VP assist page for hibernation
  1a06d017fb3f  Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM
  3704a6a44579  PM: hibernate: Propagate the return value of 
hibernation_restore()
  54e19d34011f  hv_utils: Add the support of hibernation
  ffd1d4a49336  hv_utils: Support host-initiated hibernation request
  3e9c72056ed5  hv_utils: Support host-initiated restart request
  9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns
  05bd330a7fd8  x86/hyperv: Suspend/resume the hypercall page for hibernation
  382a46221757  video: hyperv_fb: Fix hibernation for the deferred IO feature
  e2379b30324c  Input: hyperv-keyboard: Add the support of hibernation
  ac82fc8327088 PCI: hv: Add hibernation support
  a8e37506e79a  PCI: hv: Reorganize the code in preparation of hibernation
  1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource 
for hibernation
  af13f9ed6f9a  HID: hyperv: Add the support of hibernation
  25bd2b2f1f053 hv_balloon: Add the support of hibernation
  b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported()
  4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining
  0efeea5fb1535 hv_netvsc: Add the support of hibernation
  2194c2eb6717f hv_sock: Add the support of hibernation
  1ecf302021040 video: hyperv_fb: Add the support of hibernation
  56fb105859345 scsi: storvsc: Add the support of hibernation
  f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing

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

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

[Kernel-packages] [Bug 1891647] [NEW] Groovy update: v5.8.1 upstream stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   v5.8.1 upstream stable release
   from git://git.kernel.org/


scsi: ufs: Fix and simplify setup_xfer_req variant operation
USB: serial: qcserial: add EM7305 QDL product ID
USB: iowarrior: fix up report size handling for some devices
usb: xhci: define IDs for various ASMedia host controllers
usb: xhci: Fix ASMedia ASM1142 DMA addressing
Revert "ALSA: hda: call runtime_allow() for all hda controllers"
ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops
ALSA: hda/ca0132 - Add new quirk ID for Recon3D.
ALSA: hda/ca0132 - Fix ZxR Headphone gain control get value.
ALSA: hda/ca0132 - Fix AE-5 microphone selection commands.
ALSA: seq: oss: Serialize ioctls
staging: android: ashmem: Fix lockdep warning for write operation
staging: rtl8712: handle firmware load failure
Staging: rtl8188eu: rtw_mlme: Fix uninitialized variable authmode
Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt()
omapfb: dss: Fix max fclk divider for omap36xx
binder: Prevent context manager from incrementing ref 0
Smack: fix use-after-free in smk_write_relabel_self()
scripts: add dummy report mode to add_namespace.cocci
lkdtm/heap: Avoid edge and middle of slabs
vgacon: Fix for missing check in scrollback handling
mtd: properly check all write ioctls for permissions
leds: wm831x-status: fix use-after-free on unbind
leds: lm36274: fix use-after-free on unbind
leds: da903x: fix use-after-free on unbind
leds: lm3533: fix use-after-free on unbind
leds: 88pm860x: fix use-after-free on unbind
gpio: max77620: Fix missing release of interrupt
xattr: break delegations in {set,remove}xattr
Revert "powerpc/kasan: Fix shadow pages allocation failure"
powerpc/kasan: Fix shadow pages allocation failure
PCI: tegra: Revert tegra124 raw_violation_fixup
ima: move APPRAISE_BOOTPARAM dependency on ARCH_POLICY to runtime
random32: move the pseudo-random 32-bit definitions to prandom.h
random: random.h should include archrandom.h, not the other way around
arm64: kaslr: Use standard early random function
Linux 5.8.1

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux (Ubuntu Groovy)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

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

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

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.8.1 upstream stable release
+    from git://git.kernel.org/
  
-v5.8.1 upstream stable release
-from git://git.kernel.org/
+ 
+ scsi: ufs: Fix and simplify setup_xfer_req variant operation
+ USB: serial: qcserial: add EM7305 QDL product ID
+ USB: iowarrior: fix up report size handling for some devices
+ usb: xhci: define IDs for various ASMedia host controllers
+ usb: xhci: Fix ASMedia ASM1142 DMA addressing
+ Revert "ALSA: hda: call runtime_allow() for all hda controllers"
+ ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops
+ ALSA: hda/ca0132 - Add new quirk ID for Recon3D.
+ ALSA: hda/ca0132 - Fix 

[Kernel-packages] [Bug 1891405] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular wifi crashes on XPS 13 9380

[Ben Bromley]

So far, the updated firmware has worked flawlessly; no dropouts
whatsoever. I will keep my eyes out for any changes.

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:143a] Regular
  wifi crashes on XPS 13 9380

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Within the past two weeks I've been suffering from a bunch more
  crashes of my wifi on my XPS 13 9380. The wifi will stay up for awhile
  after reboot, but will eventually throw the error below and require a
  reboot.

  [26425.814726] ath10k_pci :02:00.0: firmware crashed! (guid 
63f4915b-939b-493a-8e39-2c19c0a15d9a)
  [26425.814732] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [26425.814734] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [26425.815358] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
  [26425.815910] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
4ac0889b
  [26425.815913] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [26425.826394] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [26425.826397] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [26425.826400] ath10k_pci :02:00.0: Copy Engine register dump:
  [26425.826410] ath10k_pci :02:00.0: [00]: 0x00034400  11  11   3   3
  [26425.826419] ath10k_pci :02:00.0: [01]: 0x00034800  20  19 416 417
  [26425.826427] ath10k_pci :02:00.0: [02]: 0x00034c00   1   0 127   0
  [26425.826435] ath10k_pci :02:00.0: [03]: 0x00035000   5   5   7   5
  [26425.826443] ath10k_pci :02:00.0: [04]: 0x00035400 7133 7107  34 226
  [26425.826452] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [26425.826460] ath10k_pci :02:00.0: [06]: 0x00035c00   0  30  22  20
  [26425.826468] ath10k_pci :02:00.0: [07]: 0x00036000   1   0   1   0
  [26425.860520] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [26425.940417] ieee80211 phy0: Hardware restart was requested
  [26426.161669] ath10k_pci :02:00.0: unsupported HTC service id: 1536
  [26426.285743] ath10k_pci :02:00.0: device successfully recovered

   lspci
  00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller 
(rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 
(Whiskey Lake)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th/8th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP 
Thermal Controller (rev 30)
  00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller (rev 30)
  00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP 
Serial IO I2C Controller #0 (rev 30)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP 
Serial IO I2C Controller #1 (rev 30)
  00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI 
Controller #1 (rev 30)
  00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#5 (rev f0)
  00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#7 (rev f0)
  00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#9 (rev f0)
  00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#13 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30)
  00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio 
Controller (rev 30)
  00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI 
Controller (rev 30)
  01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 

[Kernel-packages] [Bug 1891449] Re: Enable PCI ACS for platform opt to get the usb flash drive from WD19TB

[Timo Aaltonen]

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

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

Title:
  Enable PCI ACS for platform opt to get the usb flash drive from WD19TB

Status in HWE Next:
  New
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Connect with the WD19TB on the right TB port and plug the USB flash drive on 
it, the machine can't recognize the USB flash drive.

  [Fix]
  Enable the PCI ACS when Intel IOMMU is detected with platform opt in hint.

  [test]
  With the fix, the machine can recognize the USB flash drive.

  [Regression Potential]
  Low. the patch has landed on the mainline kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891449/+subscriptions

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

[Kernel-packages] [Bug 1890317] Re: Add initial audio support for Lenovo ThinkStation P620

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

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

Title:
  Add initial audio support for Lenovo ThinkStation P620

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Lenovo ThinkStation P620 is equipped with two USB audio card that don't
  fully work.

  [Fix]
  Give these two cards profile name, so userspace can identify them to add
  addition support.

  In addition to that, disable non-working element and relax error
  handling for speaker, so there's no error left. Otherwise usb-audio
  driver will stop working completely.

  [Test]
  After the patch is applied, `cat /proc/asound/cards` can show correct
  profile name for each card. No more error can be spotted from dmesg.

  The audio is still not fully working yet, because it requires more work
  in userspace ALSA and PulseAudio.

  [Regression Potential]
  Low. Adding profile name doesn't change any code flow.
  The only behavioral change is error handling towards "Speaker."
  Becuase it actually relaxes the error handling instead of tightening, so
  devices that don't have this issue won't be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890317/+subscriptions

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

[Kernel-packages] [Bug 1890231] Re: alsa: should not load sof driver if the internal mic connects to the codec

[Timo Aaltonen]

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

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

Title:
  alsa: should not load sof driver if the internal mic connects to the
  codec

Status in HWE Next:
  New
Status in linux-oem-5.6 package in Ubuntu:
  In Progress
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  This issue was introduced by #1872916 ("Support Intel Soundwire
  in 5.6-OEM Kernel 20.04"), so focal and groovy kernels don't need
  this fix.

  [Impact]
  We found the sof driver instead of hda driver is enabled on a dell
  machine without soundwire and dmic. This will make gnome show dummy
  output and users have no audio device to use.

  [Fix]
  When we integrated fix for #1872916, we backported 2 patches, these
  2 patches enable the sof driver unconditionally for Dell comet lake
  machines. There is an upstream patch to fix it, let the sof driver
  enable conditionally on comet lake machines.

  [Test Case]
  Boot the kernel with this patch on that dell machine, check the
  gnome-control-center, all audio devices exist, playback and recording
  work well.

  [Regression Risk]
  On Dell Comet Lake machines with DMIC, the sof driver should be
  enabled. Without this patch, the sof driver will be enabled unconditionally, 
but with this patch, the sof driver will be enabled conditionally, so it is 
possible to introduce a regression that on Dell Comet Lake machines, the sof 
driver is not enabled even the machine has DMIC.

  I have tested this patch on a Dell Comet Lake dmic machines, it worked
  well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890231/+subscriptions

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

[Kernel-packages] [Bug 1890441] Re: Fix missing HDMI/DP Audio on an HP Desktop

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Fix missing HDMI/DP Audio on an HP Desktop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  There's an HP desktop doesn't claim to support HDMI audio.

  [Fix] 
  Use a quirk list to force HDMI audio connection to ignore Connectivity
  Bit, which is incorrectly set by BIOS.

  [Test]
  With the patch applied, we can find HDMI codec under /proc/asound/card0
  and audio playback through HDMI works. 

  [Regression Potential] 
  This fix doesn't bring any functional change other than the targeted
  platform. The platform in question is not on the market yet so the
  risk of regression is minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890441/+subscriptions

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

[Kernel-packages] [Bug 1890306] Re: Fix IOMMU error on AMD Radeon Pro W5700

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  Fix IOMMU error on AMD Radeon Pro W5700

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  AMD Radeon Pro W5700 doesn't work at all, driver failed to probe the
  device due to IOMMU error.

  [Fix]
  Disable PCI ATS for the device.

  [Test]
  After applying the patch, there's no more IOMMU error, and the driver
  can correctly probe the device. The grahpics also works great.

  [Regression Potential] 
  Low. amdgpu is known to work well with ATS disabled. In addition to
  that, AMD confirmed it's the correct fix for this card, so the chance to
  break anything is rather low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890306/+subscriptions

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

[Kernel-packages] [Bug 1890220] Re: ASoC:amd:renoir: the dmic can't record sound after suspend and resume

[Timo Aaltonen]

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: Triaged => Fix Committed

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

Title:
  ASoC:amd:renoir:  the dmic can't record sound after suspend and resume

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  We have backported the amd renoir audio driver to oem-5.6 and focal
  kernel, recently we found if the dmic is working and we suspend and
  resume, the dmic can't record the sound after resume.

  [Fix]
  After resuming, the driver needs to restore 2 more registers, then the
  dmic could record the sound.

  [Test Case]
  Boot the kernel with this patch, open the sound-setting and run suspend
  and resume, then use arecord to record the sound, verify the sound is
  successfully recorded by aplaying it.

  [Regression Risk]
  Low, this patch is verified on the amd renoir machine, and this patch
  got ack from AMD engineer.

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

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

[Kernel-packages] [Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU

[Timo Aaltonen]

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

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

Title:
  No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7
  CPU

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  On this machine, after booting up, there is no valid sound card, the
  gnome-control-center shows a dummy output only. check the dmesg, the alsa
  sof driver fails to initialize.

  [Fix]
  Backport a patch from upstream, after applying this patch, the sof driver
  will not fail anymore even the codec driver is hda_generic

  [Test Case]
  A couple of users already test this patch on their machines, after booting
  up, there is a valid sound card, and could output sound from output devices.

  [Regression Risk]
  Low, this is cherry-picked from upstream, and this just adds a new kind of
  codec (generic) support, and a couple of ubuntu users already verified this
  patch.

  
  New focal installation on a new Acer Swift 3 laptop with core i7-1065G7.
  No sound detected, KDE/pavucontrol shows Dummy output.
  External headset also not detected.

  I've googled around and tried to reinstall alsa and pulseaudio, tried
  alsa force-reload as well. Nothing helps.

  With snd_hda_intel.dmic_detect=0 speakers start working but microphone
  is not detected. External headset detected with both headphones and
  mic. I use this as a workaround for a time being.

  I've checked
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It
  is closed  and use  recent kernel and firmware  but it does not fix my
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May  9 18:56:15 2020
  InstallationDate: Installed on 2020-04-24 (15 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Swift SF314-57G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57G
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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

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

Re: [Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

Hey, I installed Linux kernal 5.8.1-050801-generic But the problem still
persists.

On Aug 14, 2020 3:33 PM, "Anupam Jayaraj"  wrote:

> (Reading database ... 274517 files and directories currently installed.)
> Preparing to unpack 
> linux-image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb 
> ...
> Unpacking linux-image-unsigned-5.8.1-050801-generic 
> (5.8.1-050801.202008111432) over (5.8.1-050801.202008111432) ...
> dpkg: dependency problems prevent configuration of 
> linux-image-unsigned-5.8.1-050801-generic:
>  linux-image-unsigned-5.8.1-050801-generic depends on 
> linux-modules-5.8.1-050801-generic; however:
>   Package linux-modules-5.8.1-050801-generic is not installed.
>
> dpkg: error processing package linux-image-unsigned-5.8.1-050801-generic 
> (--install):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  linux-image-unsigned-5.8.1-050801-generic
>
>
>
> On Aug 14, 2020 3:18 PM, "Anupam Jayaraj"  wrote:
>
>> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/
>> linux-image-unsigned-5.8.1-050801-generic_5.8.1-050801.
>> 202008111432_amd64.deb
>> * This file cannot be installed because of unmet dependencies*
>>
>> On Aug 14, 2020 2:55 PM, "Daniel van Vugt" <1891...@bugs.launchpad.net>
>> wrote:
>>
>>> To upgrade the kernel you need to download these files:
>>>
>>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>>> headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>>> 
>>>
>>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>>> headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb
>>> 
>>>
>>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>>> image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>>> 
>>>
>>> and then in a Terminal window run:
>>>
>>>   cd ~/Downloads
>>>   sudo dpkg -i linux*.deb
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1891470
>>>
>>> Title:
>>>   [amdgpu] White screen on resume from suspend
>>>
>>> Status in linux package in Ubuntu:
>>>   Incomplete
>>> Status in mutter package in Ubuntu:
>>>   Incomplete
>>>
>>> Bug description:
>>>   The PC usually shows a Butter milk like screen when it wakes up from
>>> suspension.my laptop is set to lid close to undergo suspension.when I open
>>> the lid a paper white or Butter milk screen is shown.the only solution is
>>> to force power of by long pressing power button. this issue is also
>>> observed when the Ubuntu 20.04 OS starts.My PC is in dual boot. I play
>>> videos from Windows then shutdown Windows.On the next boot I select Ubuntu
>>> from boot options.At that time some texts are shown and after a couple of
>>> seconds this Butter milk like screen could be observed.It maybe graphics
>>> issue.
>>>   ---
>>>   ProblemType: Bug
>>>   ApportVersion: 2.20.11-0ubuntu27.6
>>>   Architecture: amd64
>>>   CasperMD5CheckResult: skip
>>>   CurrentDesktop: ubuntu:GNOME
>>>   DistroRelease: Ubuntu 20.04
>>>   InstallationDate: Installed on 2020-06-20 (54 days ago)
>>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>>> (20200423)
>>>   Package: mutter 3.36.3-0ubuntu0.20.04.1
>>>   PackageArchitecture: amd64
>>>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>>>   Tags: third-party-packages focal wayland-session
>>>   Uname: Linux 5.4.0-42-generic x86_64
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
>>> video
>>>   _MarkForUpload: True
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470
>>> /+subscriptions
>>>
>>

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

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-08-14 07:26 EDT---
Sorry for my mistake. Its not requested for xenial, -> bionic is correct...

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
 IBM z15.  This counter counts completed DEFLATE instructions
 with exit code 0, 1 or 2. Since exit code 0 means success
 and exit code 1 or 2 indicate errors, change the counter
 name to avoid confusion.  This counter is incremented each
 time the DEFLATE instruction completed regardless if an
 error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
 currently succeeds. After this patch has been applied the
 command does not work anymore. The file does not exist
 anymore. Use command 
 # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
 instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8

  Will be integrated into 20.10 by kernel 5.8 integration.

  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided

  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-08-14 06:51 EDT---
@Canonical: what is the current expectation on solving this issue. This one it 
timely critical for our upcoming offering. A comment from Canonicals side would 
be appreciated.. Many thx in advance

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

Title:
  [UBUNTU 18.04] BPF programs fail on Ubuntu s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  We need to run BPF filters to analyse and monitor network traffic. The
  BPF filters are created by skydive (http://skydive.network). Currently
  skydive fails to install BPF filters on s390x (using Ubuntu 18.04
  currently, soon moving to Ubuntu 20.04).

  Because of these failures, we decided to try the BPF samples that come
  with the kernel first. These samples also fail on s390x while they
  work fine on Intel.

  shense@boe-build:~/bionic/samples/bpf$ uname -a
  Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC 
2020 s390x s390x s390x GNU/Linux

  Example instructions:

  sudo apt install -y dpkg-dev clang llvm libelf-dev
  sudo apt-get source linux-image-unsigned-$(uname -r)
  cd linux-4.15.0/
  make headers_install
  make samples/bpf/

  Errors:

  shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map
  [sudo] password for shense:
  invalid relo for insn[4].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (b7) r1 = 0
  2: (63) *(u32 *)(r10 -32) = r1
  3: (bf) r1 = r7
  4: (85) call unknown#-1
  BPF_CALL uses reserved fields

  
  shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test
  invalid relo for insn[22].code 0x85
  bpf_load_program() err=22
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields
  0: (bf) r7 = r1
  1: (18) r1 = 0x207265743a25646e
  3: (7b) *(u64 *)(r10 -16) = r1
  4: (18) r1 = 0x705f616c6c6f632e
  6: (7b) *(u64 *)(r10 -24) = r1
  7: (18) r1 = 0x5f6c72755f686d61
  9: (7b) *(u64 *)(r10 -32) = r1
  10: (18) r1 = 0x7420737472657373
  12: (7b) *(u64 *)(r10 -40) = r1
  13: (18) r1 = 0x4661696c65642061
  15: (7b) *(u64 *)(r10 -48) = r1
  16: (b7) r1 = 0
  17: (73) *(u8 *)(r10 -8) = r1
  18: (b7) r2 = 1
  19: (7b) *(u64 *)(r10 -72) = r2
  20: (63) *(u32 *)(r10 -76) = r1
  21: (bf) r1 = r7
  22: (85) call unknown#-1
  BPF_CALL uses reserved fields

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

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

[Kernel-packages] [Bug 1891454] Patch for Ubuntu 18.04 branch master-next

[bugproxy]

--- Comment (attachment only) From tmri...@de.ibm.com 2020-08-14 03:41 
EDT---


** Attachment added: "Patch for Ubuntu 18.04 branch master-next"
   
https://bugs.launchpad.net/bugs/1891454/+attachment/5401424/+files/u18-0001-s390-cpum_cf-Add-new-extended-counters-for-IBM-z15.patch

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
 IBM z15.  This counter counts completed DEFLATE instructions
 with exit code 0, 1 or 2. Since exit code 0 means success
 and exit code 1 or 2 indicate errors, change the counter
 name to avoid confusion.  This counter is incremented each
 time the DEFLATE instruction completed regardless if an
 error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
 currently succeeds. After this patch has been applied the
 command does not work anymore. The file does not exist
 anymore. Use command 
 # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
 instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8

  Will be integrated into 20.10 by kernel 5.8 integration.

  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided

  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

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

Re: [Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

[Werner Lueckel]

Hello,
I've tested your kernel  Linux version 5.8.0+ (khfeng@ubuntu) and 
unfortunately the screen  on my system flickers again!

You may watch some videos:
flicker_5.8.0.mpg via
https://drive.google.com/file/d/1mHsmJcgkMf7H26kQSFrhccTkdOju4APe/view?usp=sharing
flicker1_5.8.0.mpg
https://drive.google.com/file/d/1683YHs3O804zgX5x7wdzl7hxyi0fSjws/view?usp=sharing
flicker2_5.8.0.mpg
https://drive.google.com/file/d/1CETTCoRWUir4o5JxPGuoMAnl9IXfAdUD/view?usp=sharing


On 12.08.20 17:40, Kai-Heng Feng wrote:
> Werner,
> Can you please test the kernel here:
> https://people.canonical.com/~khfeng/lp1861554/
>
> I'd like to see if fix for LP: #1861554 doesn't introduce a regression
> on your system.
>

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Screen flickers when using radeon.ko.
  It's a regression, it didn't happen on Trusty.

  [Fix]
  Quote the original commit log:
  "Instead of the closest reference divider prefer the lowest".

  [Test]
  Affected user confirms it fixes the issue.

  [Regression Potential]
  Low. Only affect radeaon, and it's in upstream stable tree.

  === Original Bug Report ===
  my laptop: HP Compaq nx9420
  my grafic card:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: change DFLT_CCERROR counter name

[Frank Heimes]

So if it should be applied down to xenial, it needs to be applied to
bionic, too.

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

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

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

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

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

** Changed in: ubuntu-z-systems
   Status: New => Triaged

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
 IBM z15.  This counter counts completed DEFLATE instructions
 with exit code 0, 1 or 2. Since exit code 0 means success
 and exit code 1 or 2 indicate errors, change the counter
 name to avoid confusion.  This counter is incremented each
 time the DEFLATE instruction completed regardless if an
 error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
 currently succeeds. After this patch has been applied the
 command does not work anymore. The file does not exist
 anymore. Use command 
 # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
 instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8

  Will be integrated into 20.10 by kernel 5.8 integration.

  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided

  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

[Werner Lueckel]

Hello,
I've tested the khfeng-kernel  Linux version 5.8.0+ (khfeng@ubuntu) and 
unfortunately the screen  on my system flickers again!

You may watch some videos: 
flicker_5.8.0.mpg via 
https://drive.google.com/file/d/1mHsmJcgkMf7H26kQSFrhccTkdOju4APe/view?usp=sharing
 
flicker1_5.8.0.mpg
https://drive.google.com/file/d/1683YHs3O804zgX5x7wdzl7hxyi0fSjws/view?usp=sharing
flicker2_5.8.0.mpg
https://drive.google.com/file/d/1CETTCoRWUir4o5JxPGuoMAnl9IXfAdUD/view?usp=sharing

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Screen flickers when using radeon.ko.
  It's a regression, it didn't happen on Trusty.

  [Fix]
  Quote the original commit log:
  "Instead of the closest reference divider prefer the lowest".

  [Test]
  Affected user confirms it fixes the issue.

  [Regression Potential]
  Low. Only affect radeaon, and it's in upstream stable tree.

  === Original Bug Report ===
  my laptop: HP Compaq nx9420
  my grafic card:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1852071] 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/1852071

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 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 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  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/oem-priority/+bug/1852071/+subscriptions

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

[Kernel-packages] [Bug 1884981] Re: Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot

[Patrick Then]

The bug seems present in the Intel version of the Laptop as well, filed
as Bug #1878279

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

Title:
  Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably
  fails from any given boot

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

Bug description:
  I had Windows 10 on the device and the touch pad was working
  perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs
  the touch pad stopped working at all. It doesn't appear
  /proc/bus/input/devices file.

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  danila 1249 F pulseaudio
   /dev/snd/controlC0:  danila 1249 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 24 18:00:28 2020
  InstallationDate: Installed on 2020-06-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YM
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DTCN18WW(V1.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05:
  dmi.product.family: IdeaPad 5 14ARE05
  dmi.product.name: 81YM
  dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
  dmi.product.version: IdeaPad 5 14ARE05
  dmi.sys.vendor: LENOVO

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

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

Re: [Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

(Reading database ... 274517 files and directories currently installed.)
Preparing to unpack
linux-image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
...
Unpacking linux-image-unsigned-5.8.1-050801-generic
(5.8.1-050801.202008111432) over (5.8.1-050801.202008111432) ...
dpkg: dependency problems prevent configuration of
linux-image-unsigned-5.8.1-050801-generic:
 linux-image-unsigned-5.8.1-050801-generic depends on
linux-modules-5.8.1-050801-generic; however:
  Package linux-modules-5.8.1-050801-generic is not installed.

dpkg: error processing package
linux-image-unsigned-5.8.1-050801-generic (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-unsigned-5.8.1-050801-generic


On Aug 14, 2020 3:18 PM, "Anupam Jayaraj"  wrote:

> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/
> amd64/linux-image-unsigned-5.8.1-050801-generic_5.8.1-
> 050801.202008111432_amd64.deb
> * This file cannot be installed because of unmet dependencies*
>
> On Aug 14, 2020 2:55 PM, "Daniel van Vugt" <1891...@bugs.launchpad.net>
> wrote:
>
>> To upgrade the kernel you need to download these files:
>>
>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>> headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>> 
>>
>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>> headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb
>> 
>>
>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>> image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>> 
>>
>> and then in a Terminal window run:
>>
>>   cd ~/Downloads
>>   sudo dpkg -i linux*.deb
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1891470
>>
>> Title:
>>   [amdgpu] White screen on resume from suspend
>>
>> Status in linux package in Ubuntu:
>>   Incomplete
>> Status in mutter package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   The PC usually shows a Butter milk like screen when it wakes up from
>> suspension.my laptop is set to lid close to undergo suspension.when I open
>> the lid a paper white or Butter milk screen is shown.the only solution is
>> to force power of by long pressing power button. this issue is also
>> observed when the Ubuntu 20.04 OS starts.My PC is in dual boot. I play
>> videos from Windows then shutdown Windows.On the next boot I select Ubuntu
>> from boot options.At that time some texts are shown and after a couple of
>> seconds this Butter milk like screen could be observed.It maybe graphics
>> issue.
>>   ---
>>   ProblemType: Bug
>>   ApportVersion: 2.20.11-0ubuntu27.6
>>   Architecture: amd64
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   DistroRelease: Ubuntu 20.04
>>   InstallationDate: Installed on 2020-06-20 (54 days ago)
>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>>   Package: mutter 3.36.3-0ubuntu0.20.04.1
>>   PackageArchitecture: amd64
>>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>>   Tags: third-party-packages focal wayland-session
>>   Uname: Linux 5.4.0-42-generic x86_64
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
>> video
>>   _MarkForUpload: True
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470
>> /+subscriptions
>>
>

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

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  

[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[jeremyszu]

** Package changed: linux (Ubuntu) => oem-priority

** Changed in: oem-priority
 Assignee: Kai-Heng Feng (kaihengfeng) => jeremyszu (os369510)

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 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 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  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/oem-priority/+bug/1852071/+subscriptions

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

[Kernel-packages] [Bug 1891598] Re: Broken build dep in snapcraft.yaml

[Taiten Peng]

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

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

Title:
  Broken build dep in snapcraft.yaml

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Current snapcraft.yaml is broken for building kernel snaps with ubuntu
  kernel tree from a clean ubuntu environment.

  Please see the patch in attached to fix the problem

  This is effecting Ubuntu Core developers to build a custom kernel base
  on Ubuntu stable kernel.

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

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

Re: [Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-image-
unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb

* This file cannot be installed because of unmet dependencies*

On Aug 14, 2020 2:55 PM, "Daniel van Vugt" <1891...@bugs.launchpad.net>
wrote:

> To upgrade the kernel you need to download these files:
>
>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
> headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>
>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
> headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb
>
>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
> image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>
> and then in a Terminal window run:
>
>   cd ~/Downloads
>   sudo dpkg -i linux*.deb
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891470
>
> Title:
>   [amdgpu] White screen on resume from suspend
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The PC usually shows a Butter milk like screen when it wakes up from
> suspension.my laptop is set to lid close to undergo suspension.when I open
> the lid a paper white or Butter milk screen is shown.the only solution is
> to force power of by long pressing power button. this issue is also
> observed when the Ubuntu 20.04 OS starts.My PC is in dual boot. I play
> videos from Windows then shutdown Windows.On the next boot I select Ubuntu
> from boot options.At that time some texts are shown and after a couple of
> seconds this Butter milk like screen could be observed.It maybe graphics
> issue.
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27.6
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 20.04
>   InstallationDate: Installed on 2020-06-20 (54 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   Package: mutter 3.36.3-0ubuntu0.20.04.1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>   Tags: third-party-packages focal wayland-session
>   Uname: Linux 5.4.0-42-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1891470/+subscriptions
>

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

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Daniel van Vugt]

Those are separate commands that do not print any output. You need to
run them on separate lines:

  journalctl -b-1 > prevboot.txt
  lspci -k > lspcik.txt
  dpkg -l > packages.txt

and then attach the text files they created 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/1891470

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Daniel van Vugt]

To upgrade the kernel you need to download these files:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb

and then in a Terminal window run:

  cd ~/Downloads
  sudo dpkg -i linux*.deb

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

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1891617] [NEW] Fix missing HDMI Audio on another HP Desktop

[Kai-Heng Feng]

Public bug reported:

[Impact]
There's another HP desktop doesn't claim to support HDMI audio.

[Fix]
Add the system to HDMI force connect quirk list.

[Test]
With the patch applied, we can find HDMI codec under /proc/asound/card0
and audio playback through HDMI works.

[Regression Potential] 
This fix doesn't bring any functional change other than the targeted
platform. The platform in question is not on the market yet so the
risk of regression is minimal.

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

** Affects: linux-oem-5.6 (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux-oem-5.6 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

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

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

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

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => Won't Fix

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

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

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

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

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

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

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

Title:
  Fix missing HDMI Audio on another HP Desktop

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Confirmed

Bug description:
  [Impact]
  There's another HP desktop doesn't claim to support HDMI audio.

  [Fix]
  Add the system to HDMI force connect quirk list.

  [Test]
  With the patch applied, we can find HDMI codec under /proc/asound/card0
  and audio playback through HDMI works.

  [Regression Potential] 
  This fix doesn't bring any functional change other than the targeted
  platform. The platform in question is not on the market yet so the
  risk of regression is minimal.

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

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

Re: [Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

I have run both commands *journalctl -b-1 > prevboot.txt > lspci -k >
lspci.txt*

*And*
dpkg -l > packages.txt

But no output has been given.


*Please teach me to upgrade kernel. I have poor technical knowledge:(

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

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1806439]

[navarro.ime]

I faced the same error here.

$dmesg
[2.558246] wmi_bus wmi_bus-PNP0C14:03: WQBC data block query control method 
not found
[2.584152] wmi: Failed to parse WDG method


System Information.
$ inxi -Fzx
System:Host: chivunk Kernel: 5.4.52-1-MANJARO x86_64 bits: 64 compiler: gcc 
v: 10.1.0 Desktop: Xfce 4.14.2 
   Distro: Manjaro Linux 
Machine:   Type: Convertible System: Dell product: Inspiron 7391 2n1 v: N/A 
serial:  
   Mobo: Dell model: 0070P2 v: A00 serial:  UEFI: Dell v: 1.7.0 
date: 07/10/2020 
Battery:   ID-1: BAT0 charge: 36.6 Wh condition: 36.6/45.0 Wh (81%) model: BYD 
DELL DGV2498 status: Full 
CPU:   Topology: Quad Core model: Intel Core i5-10210U bits: 64 type: MT 
MCP arch: Kaby Lake rev: C L2 cache: 6144 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 33615 
   Speed: 900 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 900 2: 
901 3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 
Graphics:  Device-1: Intel UHD Graphics vendor: Dell driver: i915 v: kernel bus 
ID: 00:02.0 
   Display: x11 server: X.Org 1.20.8 driver: intel unloaded: 
modesetting resolution: 1920x1080~60Hz, 1920x1080~60Hz 
   OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 
20.1.3 direct render: Yes 
Audio: Device-1: Intel vendor: Dell driver: snd_hda_intel v: kernel bus ID: 
00:1f.3 
   Sound Server: ALSA v: k5.4.52-1-MANJARO 
Network:   Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 
3000 bus ID: 00:14.3 
   IF: wlp0s20f3 state: up mac:  
   IF-ID-1: docker0 state: down mac:  
Drives:Local Storage: total: 476.94 GiB used: 254.29 GiB (53.3%) 
   ID-1: /dev/nvme0n1 model: H10 HBRPEKNX0202A NVMe INTEL 512GB size: 
476.94 GiB 
   ID-2: /dev/nvme1n1 model: H10 HBRPEKNX0202AO NVMe INTEL 32GB size: 
27.25 GiB

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

Title:
  wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not
  found

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

Bug description:
  Hello,

  dmesg:
  [   15.390763] wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control 
method not found

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 12:54:51 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

I did... LP: #1891518.

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2020-08-14 04:19 EDT---
This fix need to be applied to groovy, which is already documented within LP. 
But focal and xenial, need also to be added.
The backports are available for both distros.
Please update your LP entry. Many thanks in advance.
I have seen the next SRU is due 2020-08-26 !

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

Title:
  [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
  name

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:   kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
  Symptom:   Counter name CCERROR is misleading.
  Problem:   Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
 IBM z15.  This counter counts completed DEFLATE instructions
 with exit code 0, 1 or 2. Since exit code 0 means success
 and exit code 1 or 2 indicate errors, change the counter
 name to avoid confusion.  This counter is incremented each
 time the DEFLATE instruction completed regardless if an
 error was detected or not.
  Solution:  Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
  Reproduction:  Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
 currently succeeds. After this patch has been applied the
 command does not work anymore. The file does not exist
 anymore. Use command 
 # ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
 instead.
  Upstream-ID:   5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
  Component: kernel 5.8

  Will be integrated into 20.10 by kernel 5.8 integration.

  Backport available for 20.04.
  To be checked for 18.04 and 16.04, update will be provided

  Here is the backported patch.
  The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
  ("s390/cpum_cf,perf: change DFLT_CCERROR counter name")

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

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

[Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Daniel van Vugt]

Please also run:

  dpkg -l > packages.txt

and attach the resulting text file 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/1891470

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1891470] Re: [amdgpu] White screen on resume from suspend

[Daniel van Vugt]

Next time the problem happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt
  lspci -k > lspcik.txt

and attach the resulting text files here.

Please also tell us if just upgrading the kernel resolves it:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/

** Summary changed:

- Butter milk like screen
+ [amdgpu] White screen on resume from suspend

** Tags added: amdgpu

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

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

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

Title:
  [amdgpu] White screen on resume from suspend

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

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Daniel van Vugt]

If the problem doesn't fix itself by next week I say report a bug against 
Launchpad:
https://bugs.launchpad.net/launchpad

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions

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

[Kernel-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

How do we proceed with alsa-lib and alsa-ucm-conf? Since I can't attach
debdiff now...

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions

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

[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Hui Wang]

Thanks Seb.

And I verified that these 3 groovy packages worked very well on 4
machines I have.

Install the groovy daily built image on the lenovo amd renoir laptop,
enable the -proposed, install the pulseaudio_13.99.1-1ubuntu9, alsa-
lib_1.2.2-2.3ubuntu2 and alsa-ucm-conf_1.2.2-1ubuntu2, reboot. open the
gnome-sound-setting, there is digital mic in the input device list, and
It could record the sound. run suspend and resume, recheck the digital
mic, it still could record the sound. check speaker and hdmi audio, all
worked as before, plug a headset, sound could output to headphone and I
could use headset-mic to record the sound too.

Then I did the same test on a Dell dmic machine, a lenovo I+N hda audio
machine and a dell intel hda audio machine, the audio all worked as well
as before. Didn't find any regression on the new packages.

thx.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  

[Kernel-packages] [Bug 1891585] Re: alsa/sof: support 1 and 3 dmics

[Stefan Bader]

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

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

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

Title:
  alsa/sof: support 1 and 3 dmics

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-oem-5.6 package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Triaged
Status in linux-firmware source package in Focal:
  Triaged
Status in linux-oem-5.6 source package in Focal:
  Triaged
Status in linux source package in Groovy:
  Triaged
Status in linux-firmware source package in Groovy:
  Triaged

Bug description:
  This is for linux-firmware:

  [Impact]
  On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
  it alwasys report 0 dmics on the machine. So users doesn't have
  internal mic to use.

  [Fix]
  Intel provides 2 new topology files to us, they could support 1
  dmic and 3 dmics.

  [Test Case]
  Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
  the linux-firmware, the sof driver could detect the dmic and users
  have a workable internal mic after booting up.

  [Regression Risk]
  This is adding 2 new topology files, not changing anything on
  current sof-firmware, so the regression posibility is very low.

  This is for linux kernel:

  [Impact]
  On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
  it alwasys report 0 dmics on the machine. So users doesn't have
  internal mic to use.

  [Fix]
  Intel write a patch to fix this issue, if NHLT table returns 1 or
  3 dmics, the sof driver will not fail like before, it can support
  1 or 3 dmics after applying this patch.

  [Test Case]
  Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
  the linux-firmware, the sof driver could detect the dmic and users
  have a workable internal mic after booting up.

  [Regression Risk]
  This patch adds new support for 1 and 3 dmics, it doesn't change
  anything on existing functions, so the regression posibility is very
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891585/+subscriptions

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

[Kernel-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Daniel van Vugt]

No problem, you can get the patch here:

https://git.launchpad.net/~ubuntu-audio-
dev/pulseaudio/patch/?id=c1e070769e351f529d34263301fad6ff141ff456

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions

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

[Kernel-packages] [Bug 1891528] Re: fix ftrace pid filtering on linux 5.8

[Stefan Bader]

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

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

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

Title:
  fix ftrace pid filtering on linux 5.8

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Groovy:
  Triaged

Bug description:
  A couple of ftrace kernel self test regression tests are failing on
  systems with 1 CPU, notably small 1 CPU cloud instances. The two
  tests that are failing are:

  [20] ftrace - function graph filters with stack tracer  
  [21] ftrace - function graph filters

  Bisected this down to commit 717e3f5ebc82 ("ftrace: Make function
  trace pid filtering a bit more exact") in linux 5.6-rc4 and found
  and tested an upstream fix to this issue with the commit
  c58b6b0372de ("ftrace: Fix ftrace_trace_task return value").

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

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

[Kernel-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

Thanks. Rebased and pushed.

However, I can't attach the debdiff here because I am still hitting
Launchpad Oops - LP: #1891518.

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions

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

[Kernel-packages] [Bug 1891451] Re: Add TGL+ SAGV display support

[You-Sheng Yang]

Also verified 5.8 kernel version 5.8.0-16 from ppa:canonical-kernel-
team/bootstrap doesn't have this issue, so we may close the Groovy part
when it upgrades to 5.8.

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

Title:
  Add TGL+ SAGV display support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  On platforms with UHD panel, massive drawing area updates may cause
  screen to flash as half-baked render buffers with black areas being
  renedered.

  [Fix]

  This turns out to be the lack of full support to Intel System Agent
  Geyserville (SAGV), which has been landed to kernel v5.8. The required
  fix resides in https://patchwork.freedesktop.org/series/75129/, which
  seems a rolling set that its early parts have been committed separatedly
  several times. This patchset also depends on
  https://patchwork.freedesktop.org/series/72301/, which attempts to make
  global state handling more standardized.

  [Test Case]

  1. Trigger massive rect updates, e.g. cat a lengthy file in xterm, dump
  kernel git history, etc.
  2. Observe if screen flashes with half black panes, sometimes black
  stripes, etc.

  [Regression Potential]
  Medium. This is to backport a new feature landed to kernel early this
  year, even there is no later fixes patch found so far, it could still
  introduce incompatibility to older kernels. So far it behaves on both
  UHD and other lower resolutions.

  == Original Bug Description ==

  On platforms with UHD panel, massive drawing area updates may cause
  screen to flash as half-baked render buffers with black areas being
  renedered.

  [Reproduce Steps]
  1. boot to GUI
  2. generate massive screen updates by `while true; do dmesg; done` or so

  [Results]
  Expected Result:
  Text output correctly rendered on xterm smoothly

  Actual Result:
  Screen flashes with black strides, etc.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1855 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X35
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enx00e04c6801fa  no wireless extensions.
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=00ec17d2-a1e3-4363-a67b-a7c380cc9189 ro drm.debug=0x1ff 
log_buf_len=32M
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1020-oem N/A
   linux-backports-modules-5.6.0-1020-oem  N/A
   linux-firmware  1.187.2
  RfKill:

  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.9
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: 202007-28063
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.9:bd07/30/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891451/+subscriptions

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

[Kernel-packages] [Bug 1891451] Re: Add TGL+ SAGV display support

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-
team/2020-August/112675.html

** Description changed:

- TBD.
- --- 
+ [SRU Justification]
+ 
+ [Impact]
+ 
+ On platforms with UHD panel, massive drawing area updates may cause
+ screen to flash as half-baked render buffers with black areas being
+ renedered.
+ 
+ [Fix]
+ 
+ This turns out to be the lack of full support to Intel System Agent
+ Geyserville (SAGV), which has been landed to kernel v5.8. The required
+ fix resides in https://patchwork.freedesktop.org/series/75129/, which
+ seems a rolling set that its early parts have been committed separatedly
+ several times. This patchset also depends on
+ https://patchwork.freedesktop.org/series/72301/, which attempts to make
+ global state handling more standardized.
+ 
+ [Test Case]
+ 
+ 1. Trigger massive rect updates, e.g. cat a lengthy file in xterm, dump
+ kernel git history, etc.
+ 2. Observe if screen flashes with half black panes, sometimes black
+ stripes, etc.
+ 
+ [Regression Potential]
+ Medium. This is to backport a new feature landed to kernel early this
+ year, even there is no later fixes patch found so far, it could still
+ introduce incompatibility to older kernels. So far it behaves on both
+ UHD and other lower resolutions.
+ 
+ == Original Bug Description ==
+ 
+ On platforms with UHD panel, massive drawing area updates may cause
+ screen to flash as half-baked render buffers with black areas being
+ renedered.
+ 
+ [Reproduce Steps]
+ 1. boot to GUI
+ 2. generate massive screen updates by `while true; do dmesg; done` or so
+ 
+ [Results]
+ Expected Result:
+ Text output correctly rendered on xterm smoothly
+ 
+ Actual Result:
+ Screen flashes with black strides, etc.
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  u  1855 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1855 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X35
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X35
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
-  lono wireless extensions.
-  
-  enx00e04c6801fa  no wireless extensions.
+  lono wireless extensions.
+ 
+  enx00e04c6801fa  no wireless extensions.
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem 
root=UUID=00ec17d2-a1e3-4363-a67b-a7c380cc9189 ro drm.debug=0x1ff 
log_buf_len=32M
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.6.0-1020-oem N/A
-  linux-backports-modules-5.6.0-1020-oem  N/A
-  linux-firmware  1.187.2
+  linux-restricted-modules-5.6.0-1020-oem N/A
+  linux-backports-modules-5.6.0-1020-oem  N/A
+  linux-firmware  1.187.2
  RfKill:
-  
+ 
  Tags:  focal
  Uname: Linux 5.6.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.9
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: 202007-28063
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.9:bd07/30/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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

Title:
  Add TGL+ SAGV display support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  On platforms with UHD panel, massive drawing area updates may cause
  screen to flash as half-baked render buffers with black areas 

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

[Ubuntu Kernel Bot]

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

apport-collect 1891598

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

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

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

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

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

Title:
  Broken build dep in snapcraft.yaml

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Current snapcraft.yaml is broken for building kernel snaps with ubuntu
  kernel tree from a clean ubuntu environment.

  Please see the patch in attached to fix the problem

  This is effecting Ubuntu Core developers to build a custom kernel base
  on Ubuntu stable kernel.

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

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

[Kernel-packages] [Bug 1891598] [NEW] Broken build dep in snapcraft.yaml

[Taiten Peng]

Public bug reported:

Current snapcraft.yaml is broken for building kernel snaps with ubuntu
kernel tree from a clean ubuntu environment.

Please see the patch in attached to fix the problem

This is effecting Ubuntu Core developers to build a custom kernel base
on Ubuntu stable kernel.

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

Title:
  Broken build dep in snapcraft.yaml

Status in linux package in Ubuntu:
  New

Bug description:
  Current snapcraft.yaml is broken for building kernel snaps with ubuntu
  kernel tree from a clean ubuntu environment.

  Please see the patch in attached to fix the problem

  This is effecting Ubuntu Core developers to build a custom kernel base
  on Ubuntu stable kernel.

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

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

[Kernel-packages] [Bug 1891585] Re: alsa/sof: support 1 and 3 dmics

[Hui Wang]

** Description changed:

- This is for trackig purpose.
+ This is for linux-firmware:
+ 
+ [Impact]
+ On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
+ it alwasys report 0 dmics on the machine. So users doesn't have
+ internal mic to use.
+ 
+ [Fix]
+ Intel provides 2 new topology files to us, they could support 1
+ dmic and 3 dmics.
+ 
+ [Test Case]
+ Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
+ the linux-firmware, the sof driver could detect the dmic and users
+ have a workable internal mic after booting up.
+ 
+ [Regression Risk]
+ This is adding 2 new topology files, not changing anything on
+ current sof-firmware, so the regression posibility is very low.
+ 
+ This is for linux kernel:
+ 
+ [Impact]
+ On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
+ it alwasys report 0 dmics on the machine. So users doesn't have
+ internal mic to use.
+ 
+ [Fix]
+ Intel write a patch to fix this issue, if NHLT table returns 1 or
+ 3 dmics, the sof driver will not fail like before, it can support
+ 1 or 3 dmics after applying this patch.
+ 
+ [Test Case]
+ Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
+ the linux-firmware, the sof driver could detect the dmic and users
+ have a workable internal mic after booting up.
+ 
+ [Regression Risk]
+ This patch adds new support for 1 and 3 dmics, it doesn't change
+ anything on existing functions, so the regression posibility is very
+ low.

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

Title:
  alsa/sof: support 1 and 3 dmics

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged
Status in linux-oem-5.6 package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Triaged
Status in linux-firmware source package in Focal:
  Triaged
Status in linux-oem-5.6 source package in Focal:
  Triaged
Status in linux source package in Groovy:
  Triaged
Status in linux-firmware source package in Groovy:
  Triaged

Bug description:
  This is for linux-firmware:

  [Impact]
  On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
  it alwasys report 0 dmics on the machine. So users doesn't have
  internal mic to use.

  [Fix]
  Intel provides 2 new topology files to us, they could support 1
  dmic and 3 dmics.

  [Test Case]
  Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
  the linux-firmware, the sof driver could detect the dmic and users
  have a workable internal mic after booting up.

  [Regression Risk]
  This is adding 2 new topology files, not changing anything on
  current sof-firmware, so the regression posibility is very low.

  This is for linux kernel:

  [Impact]
  On a Dell tigerlake laptop, the sof driver fails to detect the dmic,
  it alwasys report 0 dmics on the machine. So users doesn't have
  internal mic to use.

  [Fix]
  Intel write a patch to fix this issue, if NHLT table returns 1 or
  3 dmics, the sof driver will not fail like before, it can support
  1 or 3 dmics after applying this patch.

  [Test Case]
  Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in
  the linux-firmware, the sof driver could detect the dmic and users
  have a workable internal mic after booting up.

  [Regression Risk]
  This patch adds new support for 1 and 3 dmics, it doesn't change
  anything on existing functions, so the regression posibility is very
  low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891585/+subscriptions

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