date:20200816

Hi @jeremyn54

> the error can be consistently reproduced on both signed and testing
kernels.

Reproduced on the test kernel? The one that I built in the ppa? If
that's the case, then "usb: handle warm-reset port requests on hub
resume" might not be to blame after all.

I had a look at your kernel log:

> usb usb4-port2: Cannot enable. Maybe the USB cable is bad?

The bad device is usb4-port2 in your system. The log's don't show what
device this is. It only mentions the root hub, and not the device:

usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: xHCI Host Controller
usb usb4: Manufacturer: Linux 5.4.0-42-generic xhci-hcd
usb usb4: SerialNumber: :00:14.0

We need to know what device is plugged into "port 2" of that hub, i.e.
"usb 4-2". Can you try determine what the device is?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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

Re: [Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend

2020-08-16 Thread Ryan

Thank you. I dont know how i did not see that before

On Mon, Aug 17, 2020 at 12:25 AM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:

> Also, please don't use Alt+F2. This command needs to be run in the
> Terminal app:
>
>   journalctl -b-1 > prevboot.txt
>
> But only using the steps from comment #2. And then use the Files app to
> retrieve the file.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891684
>
> Title:
>   [amdgpu] Screen flickers after resuming from suspend
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when computer is coming out of suspension mode, i get terrible screen
>   flickers. Only way i have worked around this is a reboot.
>
>   This video card is from sapphire
>   Nitro + SE 5700xt
>
>   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: Fri Aug 14 12:16:42 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
> XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
>  Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600
> OEM/5600 XT / 5700/5700 XT] [1da2:e410]
>   InstallationDate: Installed on 2020-06-08 (66 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: System manufacturer System Product Name
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic
> root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/17/2020
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 2203
>   dmi.board.asset.tag: Default string
>   dmi.board.name: TUF GAMING X570-PLUS
>   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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+subscriptions
>


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1891684/+attachment/5402050/+files/prevboot.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/1891684

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  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: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:

[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

Wrote to debian-devel to see if upstream is interested in carrying the
debian postinstall changes for util-linux: https://lists.debian.org
/debian-devel/2020/08/msg00107.html

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Committed
Status in procps package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in procps source package in Groovy:
  In Progress
Status in util-linux source package in Groovy:
  In Progress

Bug description:
  [Impact]

  This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT
  feature by default for Groovy onward, proposed to ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html

  The kernel log buffer contains a wealth of sensitive information, such
  as detailed call traces and kernel addresses found in register dumps
  in kernel oops messages.

  Exploit developers and attackers can leverage these information leaks
  to get past KASLR, and they can use the kernel log buffer to get
  instant feedback on their privilege escalation attacks, as failures
  will be shown as further oops messages, which attackers can use to fix
  and tune their programs until they work.

  Currently, if I create a new, unprivileged user on a Focal system,
  they cannot access /var/log/kern.log, /var/log/syslog or see system
  events in journalctl. But yet, they are given free reign to the kernel
  log buffer.

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ cat /var/log/kern.log
  cat: /var/log/kern.log: Permission denied
  $ cat /var/log/syslog
  cat: /var/log/syslog: Permission denied
  $ journalctl
  Hint: You are currently not seeing messages from other users and the system.
    Users in groups 'adm', 'systemd-journal' can see all messages.
    Pass -q to turn off this notice.
  Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target.
  Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms.
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  I propose that we restrict access to dmesg to users in group 'adm'
  like so:

  1) Add kernel.dmesg_restrict = 1 to
 /etc/sysctl.d/10-kernel-hardening.conf
  2) Following changes to /bin/dmesg permissions in package 'util-linux'
  - Ownership changes to root:adm
  - Permissions changed to 0750 (-rwxr-x---)
  - Add cap_syslog capability to binary.

  For most users, they will use the initial admin account, which is in
  the 'adm' group already, and will see no impact to these changes. If a
  log scraper type program needs access to dmesg, the user the daemon
  runs as can simply be added to the 'adm' group.

  [Testcase]

  Currently, all users can run /usr/bin/dmesg to view the kernel log
  buffer:

  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  When the changes are applied, the default admin user will be able to
  view dmesg (since they are in group 'adm'), while new unprivileged
  users will not.

  Test packages are available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test

  $ whoami
  ubuntu
  $ groups
  ubuntu adm cdrom sudo dip plugdev
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ dmesg
  -bash: /usr/bin/dmesg: Permission denied

  [Regression Potential]

  Some users or log scraper type programs may need to view the kernel
  log buffer, or have access to dmesg. In this case, the underlying
  service user would need to be added to the 'adm' group.

  Users have the ability to disable DMESG_RESTRICT by changing
  kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf
  from '1' to '0', followed by a reboot.

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

-- 
Mailing list:

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

2020-08-16 Thread gannon1

@John Hoff

Darn. Let's try something else.

I submitted a kernel patch adding model=alc298-samsung-headphone (see
attached). It exposes the quirk that fixed my Samsung Notebook 9 Pro as
a "model" option that you can pass to snd_hda_intel. Give it a try:

1) Apply my patch to the linux kernel, compile, and run it.
(Alternatively, wait until my patch lands in your favorite linux
distribution's kernel binary and then upgrade.)

2) echo "options snd-hda-intel model=alc298-samsung-headphone" >
/etc/modprobe.d/alsa-base.conf

3) Reboot

I tested on my Samsung Notebook 9 Pro (NP930MBE-K04US) which runs Arch.
The filename in step 2) might be different for Ubuntu.

** Patch added: "0001-ALSA-hda-realtek-Add-model-alc298-samsung-headphone.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851518/+attachment/5402049/+files/0001-ALSA-hda-realtek-Add-model-alc298-samsung-headphone.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/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,

[Kernel-packages] [Bug 1880334] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

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

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

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

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  portion of bug report for bionic:

  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

  NOTE: I'm experiencing this with focal repeatedly - just hangs
  forever!

  ubunutu 20.04 server - live

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1880334/+subscriptions

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

[Kernel-packages] [Bug 1882945] Re: snd_hda_intel blocks/freezes suspend

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

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

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

Title:
  snd_hda_intel blocks/freezes suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since some packages upgrade(probalby couple months back; when I had
  LTS bionic) I'm unable to suspend my PC.

  I thought installing newest LTS focal will solve this problem but it
  didn't - system freezes on suspend displaying plymouth last screen.

  I found debug howto here :
  https://www.kernel.org/doc/Documentation/power/s2ram.txt

  What I found according to it:

  lut 21 09:43:39 pc kernel: PM:   Magic number: 0:88:726
  lut 21 09:43:39 pc kernel: PM:   hash matches drivers/base/power/main.c:1721
  lut 21 09:43:39 pc kernel: block loop6: hash matches
  lut 21 09:43:39 pc kernel: pci :01:00.1: hash matches
  lut 21 09:43:39 pc kernel: rtc_cmos 00:06: setting system clock to 
2060-02-21T08:43:23 UTC (2844578603)

  $ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Complex
  00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 30h-3fh) 
I/O Memory Management Unit
  00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Kaveri P2P Bridge for 
GFX PCIe Port [1:0]
  00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Root Port
  00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
  00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI 
Controller (rev 09)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA 
Controller [AHCI mode] (rev 40)
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI 
Controller (rev 11)
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 
16)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD] FCH IDE Controller
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller (rev 01)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40)
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI 
Controller (rev 11)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 0
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 1
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 2
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 3
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 4
  00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 
30h-3fh) Processor Function 5
  01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
  marcin@pc:/sys

  
  $ ls /sys/devices/pci* 
  :00:00.0  :00:02.1  :00:04.0  :00:11.0  :00:13.0  
:00:14.1  :00:14.4  :00:18.1  :00:18.4   pci_bus
  :00:00.2  :00:03.0  :00:10.0  :00:12.0  :00:13.2  
:00:14.2  :00:14.5  :00:18.2  :00:18.5   power
  :00:02.0  :00:03.1  :00:10.1  :00:12.2  :00:14.0  
:00:14.3  :00:18.0  :00:18.3  firmware_node  uevent

  
  $ cat /sys/power/pm_trace_dev_match
  resulted in: block and snd_hda_intel

  as I was unable to force :
  $ modprobe -r -f snd_hda_intel
  modprobe: FATAL: Module snd_hda_intel is in use.

  I did change /etc/default/grub to:
  GRUB_CMDLINE_LINUX="snd_hda_intel.blacklist=1 
modprobe.blacklist=snd_hda_intel"

  then sudo grub-update.

  After reboot suspend was finnaly working correctly 
  but I've NO sound now:(

  
  Googling on the internet I found:

[Kernel-packages] [Bug 1876470] Re: no sound Asus Strix II

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

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

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

Title:
  no sound Asus Strix II

Status in linux package in Ubuntu:
  Expired

Bug description:
  ref. bug 1784485

  I'm experiencing the same bug as per the one above.It was fixed with
  the previous kernel version, now it came back.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imre   2276 F pulseaudio
   /dev/snd/pcmC0D0p:   imre   2276 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 17:15:58 2020
  InstallationDate: Installed on 2020-04-24 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1869 ASUSTek Computer, Inc. ITE Device(8910)
   Bus 001 Device 002: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Strix 15 GL503GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=d7a06f9f-6933-4c73-a3c1-576bfdc8d86f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-28-generic N/A
   linux-backports-modules-5.4.0-28-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503GE.316
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503GE
  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.:bvrGL503GE.316:bd07/19/2019:svnASUSTeKCOMPUTERINC.:pnStrix15GL503GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503GE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Strix
  dmi.product.name: Strix 15 GL503GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1880334] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

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

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  portion of bug report for bionic:

  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

  NOTE: I'm experiencing this with focal repeatedly - just hangs
  forever!

  ubunutu 20.04 server - live

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1880334/+subscriptions

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

[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend

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

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

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

Title:
  USB 3.1 Gen 1 not work after using suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Good morning.

  I use "suspend"(settings -> energy -> When the shutdown...) on 18.04.

  Each wake up, USB ports 3.1 Gen 1 don't work (only those on the
  motherboard on the back of the case).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christophe   1648 F pulseaudio
   /dev/snd/controlC2:  christophe   1648 F pulseaudio
   /dev/snd/controlC0:  christophe   1648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-02-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x)

  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 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.15
  RfKill:

  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---

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

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

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

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

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

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

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

Status in linux package in Ubuntu:
  Expired

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

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

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

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

[Kernel-packages] [Bug 1824175] Re: iGVT-g guest does not load graphics: kernel WARNING and wedged GPU

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

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

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

Title:
  iGVT-g guest does not load graphics: kernel WARNING and wedged GPU

Status in linux package in Ubuntu:
  Expired

Bug description:
  On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel
  GVT-g guest, it was noticed that the graphical interface does not
  load. The following message appears:

  [   19.844904] i915 :00:03.0: Failed to initialize GPU, declaring
  it wedged!

  And there are two kernel WARNING that appear. The first WARNING seems
  harmless and it was already reported:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is
  related to the host kernel, on this case 4.18.0-17 from HWE.

  The second WARNING is new and probably is related to the failure to
  load the graphics.

  It is possible to access the guest using the serial console. While the
  system claims GDM is working, there is no graphical interface visible.

  I have tested with Xubuntu 19.04 Disco Dingo Beta too and the same
  problem was noticed: two kernel WARNING, a wedged GPU and failure to
  load the graphics, even if the LightDM services was shown as running
  by systemctl status.

  Ubuntu 18.04 guests with kernel 4.15 and 4.18 are working. Mageia 7
  guests with kernel 5.0.7 are working too, this seems related to the
  5.0.0 kernel from Disco. Tested with both 5.0.0-7 and 5.0.0-8.

  Example of QEMU command line used:

  qemu-system-x86_64 -global PIIX4_PM.disable_s4=1 -M pc,usb=false
  -machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -name "Ubuntu
  Disco" -k pt-br -nodefaults -accel kvm -m 2G -cpu host -smp
  cores=2,threads=1 -netdev user,id=net0 -device
  e1000,netdev=net0,addr=8 -device vfio-
  pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/84de120a-c340-48fc-
  ba40-62f54c76f3ad,rombar=0,display=on,addr=0x3,id=iHD520 -device nec-
  usb-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 -device
  usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display
  gtk,gl=on -hda
  /home/usuario/.local/share/libvirt/images/ubuntu_disco.qcow2 -monitor
  vc -serial vc

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: User Name 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Apr 10 12:04:47 2019
  InstallationDate: Installed on 2019-04-09 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 002: ID 46f4:0002  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=deb9f102-2eaf-4c05-96da-8c541c55726b ro quiet splash console=ttyS0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.1
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend

If you open the 'Files' app then you should be able to find the file
'prevboot.txt' in your Home folder.

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

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  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: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT 
/ 5700/5700 XT] [1da2:e410]
  InstallationDate: Installed on 2020-06-08 (66 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2203
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS
  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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+subscriptions

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

[Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend

Also, please don't use Alt+F2. This command needs to be run in the
Terminal app:

  journalctl -b-1 > prevboot.txt

But only using the steps from comment #2. And then use the Files app to
retrieve the file.

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

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  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: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT 
/ 5700/5700 XT] [1da2:e410]
  InstallationDate: Installed on 2020-06-08 (66 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2203
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS
  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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+subscriptions

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

[Kernel-packages] [Bug 1890930] Re: Xorg freeze

In case the freeze was actually a crash somewhere, please try following
these instructions:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Summary changed:

- Xorg freeze
+ [amdgpu] Xorg freeze

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

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

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

Title:
  [amdgpu] Xorg freeze

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

Bug description:
  Ubuntu freeze randomly 
  My laptop is AMD ryzen 5 2500U 
  GPU TADEON VEGA GRAPHIC

  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: Sun Aug  9 13:37:02 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:84ae]
  InstallationDate: Installed on 2020-04-25 (105 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Laptop 15-db0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8fad8780-5a61-47b5-8c26-63fbc3a59d18 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84AE
  dmi.board.vendor: HP
  dmi.board.version: 86.20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/31/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-db0xxx
  dmi.product.sku: 4PC77PA#AKL
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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/1890930/+subscriptions

-- 
Mailing list: https://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 1891684] Re: [amdgpu] Screen flickers after resuming from suspend

2020-08-16 Thread Ryan

need a little more help than than. Im new to Ubuntu. I dont know how to
navigate

On Sun, Aug 16, 2020 at 11:55 PM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:

> The file should be created in the directory you ran the command so look
> there:
>
>   journalctl -b-1 > prevboot.txt
>   ls *.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891684
>
> Title:
>   [amdgpu] Screen flickers after resuming from suspend
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when computer is coming out of suspension mode, i get terrible screen
>   flickers. Only way i have worked around this is a reboot.
>
>   This video card is from sapphire
>   Nitro + SE 5700xt
>
>   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: Fri Aug 14 12:16:42 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
> XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
>  Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600
> OEM/5600 XT / 5700/5700 XT] [1da2:e410]
>   InstallationDate: Installed on 2020-06-08 (66 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: System manufacturer System Product Name
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic
> root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/17/2020
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 2203
>   dmi.board.asset.tag: Default string
>   dmi.board.name: TUF GAMING X570-PLUS
>   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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+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/1891684

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  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: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology

[Kernel-packages] [Bug 1891821] Re: Laptop Heats up

Please double-check CPU usage by running 'top' in a Terminal window. Any
high CPU users there?

If not then this sounds like a radeon kernel issue.

** Tags added: hybrid radeon

** Summary changed:

- Laptop Heats up
+ [radeon] Laptop Heats up

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

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

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

Title:
  [radeon] Laptop Heats up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hp pavilion g6 2238tx overheating issue. not indicating high CPU
  usage. assume somethings wrong with graphic drivers

  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: Mon Aug 17 02:43:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1842]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2020-07-27 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=fab59395-a336-41f1-bd2f-edff59968339 ro quiet splashs
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1842
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr087A11385B1620100:rvnHewlett-Packard:rn1842:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4B20PA#ABG
  dmi.product.version: 087A11385B1620100
  dmi.sys.vendor: Hewlett-Packard
  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/1891821/+subscriptions

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

[Kernel-packages] [Bug 1891821] [NEW] [radeon] Laptop Heats up

You have been subscribed to a public bug:

Hp pavilion g6 2238tx overheating issue. not indicating high CPU usage.
assume somethings wrong with graphic drivers

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: Mon Aug 17 02:43:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1842]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2020-07-27 (20 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=fab59395-a336-41f1-bd2f-edff59968339 ro quiet splashs
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1842
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr087A11385B1620100:rvnHewlett-Packard:rn1842:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.sku: D4B20PA#ABG
dmi.product.version: 087A11385B1620100
dmi.sys.vendor: Hewlett-Packard
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

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


** Tags: amd64 apport-bug focal hybrid radeon ubuntu
-- 
[radeon] Laptop Heats up
https://bugs.launchpad.net/bugs/1891821
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

** Tags added: focal

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  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.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend

The file should be created in the directory you ran the command so look
there:

  journalctl -b-1 > prevboot.txt
  ls *.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/1891684

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  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: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT 
/ 5700/5700 XT] [1da2:e410]
  InstallationDate: Installed on 2020-06-08 (66 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2203
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS
  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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+subscriptions

-- 
Mailing list: https://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 1891684] Re: screen flickers

2020-08-16 Thread Ryan

i am not recieving a text file when i run the command
what am i doing wrong?
alt+f2 to bring up command
i have rebooted, suspended, reproduced flicker, rebooted then entered
verbatim. No text file appears?


On Sun, Aug 16, 2020 at 10:40 PM Daniel van Vugt <1891...@bugs.launchpad.net>
wrote:

> Please:
>
> 1. Reboot again.
>
> 2. Suspend, resume, and reproduce the flicker.
>
> 3. Reboot yet again.
>
> 4. Run this command:
>
>journalctl -b-1 > prevboot.txt
>
>and attach the resulting text file here.
>
> ** Tags added: amdgpu
>
> ** Summary changed:
>
> - screen flickers
> + [amdgpu] screen flickers
>
> ** Tags added: suspend-resume
>
> ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
>
> ** Summary changed:
>
> - [amdgpu] screen flickers
> + [amdgpu] Screen flickers after resuming from suspend
>
> ** Also affects: linux (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891684
>
> Title:
>   [amdgpu] Screen flickers after resuming from suspend
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when computer is coming out of suspension mode, i get terrible screen
>   flickers. Only way i have worked around this is a reboot.
>
>   This video card is from sapphire
>   Nitro + SE 5700xt
>
>   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: Fri Aug 14 12:16:42 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
> XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
>  Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600
> OEM/5600 XT / 5700/5700 XT] [1da2:e410]
>   InstallationDate: Installed on 2020-06-08 (66 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: System manufacturer System Product Name
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic
> root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/17/2020
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 2203
>   dmi.board.asset.tag: Default string
>   dmi.board.name: TUF GAMING X570-PLUS
>   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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+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/1891684

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this

[Kernel-packages] [Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19

2020-08-16 Thread Leon Liao

Changed this bug status to fix released. Because of the original bug
1849812 has been fix released.

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  usb-audio: the mic can't record any sound after resume on Dell Dock
  WD19

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  There is a heaset jack on the dock, after resume, the mic on that jack
  can't record sound anymore, need to close the recording app then reopen
  that app to workaround this issue.

  [Fix]
  set the interface and EP, then the mic can record sound again.

  
  [Test Case]
  test the kernel with this patch, the mic can record sound after resume.

  [Regression Risk]
  Low, this quirk is specific to WD19 (usb vednor and device id).

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

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

2020-08-16 Thread Hui Wang

@Seb,

Pushed the changes to pulseaudio Vcs ubuntu-focal branch. Is there
anything need to change before uploading to focal building queue?

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 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
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch

[Kernel-packages] [Bug 1891684] Re: screen flickers

Please:

1. Reboot again.

2. Suspend, resume, and reproduce the flicker.

3. Reboot yet again.

4. Run this command:

   journalctl -b-1 > prevboot.txt

   and attach the resulting text file here.

** Tags added: amdgpu

** Summary changed:

- screen flickers
+ [amdgpu] screen flickers

** Tags added: suspend-resume

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Summary changed:

- [amdgpu] screen flickers
+ [amdgpu] Screen flickers after resuming from suspend

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

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

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

Title:
  [amdgpu] Screen flickers after resuming from suspend

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

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  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: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT 
/ 5700/5700 XT] [1da2:e410]
  InstallationDate: Installed on 2020-06-08 (66 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2203
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS
  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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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/1891684/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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] Status changed to Confirmed

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

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

Status in linux package in Ubuntu:
  Confirmed

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 1891470] Re: [amdgpu] White screen on resume from suspend

If you launch the 'Additional Drivers' app, can you install the "pro"
drivers from there?

Also please remember to run the commands in comment #10.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

** Summary changed:

- Cannot switch to A2DP profile w/o restarting bluetooth.service
+ Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: 
Refused to switch profile to a2dp_sink: Not connected]

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

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

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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

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

Perfect, thanks. That shows the 'amdgpu' kernel driver is crashing in a
couple of ways.

** Summary changed:

- [amdgpu] Display does not come on after suspend
+ [amdgpu] Display does not come on after suspend (amdgpu crashes)

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

** Tags added: suspend-resume

-- 
You 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 (amdgpu crashes)

Status in linux package in Ubuntu:
  Confirmed

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 1837810] Re: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host

Attached is a kernel module which lets you see the contents of the
zero_page reference counter, and to set it to near overflow.

** Attachment added: "kernel module to view zero_page reference counter"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837810/+attachment/5402014/+files/zero_page_refcount.c

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

Title:
  KVM: Fix zero_page reference counter overflow when using KSM on KVM
  compute host

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1837810

  [Impact]

  We are seeing a problem on OpenStack compute nodes, and KVM hosts,
  where a kernel oops is generated, and all running KVM machines are
  placed into the pause state.

  This is caused by the kernel's reserved zero_page reference counter
  overflowing from a positive number to a negative number, and hitting a
  (WARN_ON_ONCE(page_ref_count(page) <= 0)) condition in try_get_page().

  This only happens if the machine has Kernel Samepage Mapping (KSM)
  enabled, with "use_zero_pages" turned on. Each time a new VM starts
  and the kernel does a KSM merge run during a EPT violation, the
  reference counter for the zero_page is incremented in try_async_pf()
  and never decremented. Eventually, the reference counter will
  overflow, causing the KVM subsystem to fail.

  Syslog:
  error : qemuMonitorJSONCheckError:392 : internal error: unable to execute 
QEMU command 'cont': Resetting the Virtual Machine is required

  QEMU Logs:
  error: kvm run failed Bad address
  EAX=000afe00 EBX=000b ECX=0080 EDX=0cfe
  ESI=0003fe00 EDI=000afe00 EBP=0007 ESP=6d74
  EIP=000ee344 EFL=00010002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =0010   00c09300 DPL=0 DS   [-WA]
  CS =0008   00c09b00 DPL=0 CS32 [-RA]
  SS =0010   00c09300 DPL=0 DS   [-WA]
  DS =0010   00c09300 DPL=0 DS   [-WA]
  FS =0010   00c09300 DPL=0 DS   [-WA]
  GS =0010   00c09300 DPL=0 DS   [-WA]
  LDT=   8200 DPL=0 LDT
  TR =   8b00 DPL=0 TSS32-busy
  GDT= 000f7040 0037
  IDT= 000f707e 
  CR0=0011 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=c3 57 56 b8 00 fe 0a 00 be 00 fe 03 00 b9 80 00 00 00 89 c7  a5 a1 
00 80 03 00 8b 15 04 80 03 00 a3 00 80 0a 00 89 15 04 80 0a 00 b8 ae e2 00 00 31

  Kernel Oops:

  [  167.695986] WARNING: CPU: 1 PID: 3016 at 
/build/linux-hwe-FEhT7y/linux-hwe-4.15.0/include/linux/mm.h:852 
follow_page_pte+0x6f4/0x710
  [  167.696023] CPU: 1 PID: 3016 Comm: CPU 0/KVM Tainted: G   OE
4.15.0-106-generic #107~16.04.1-Ubuntu
  [  167.696023] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1 04/01/2014
  [  167.696025] RIP: 0010:follow_page_pte+0x6f4/0x710
  [  167.696026] RSP: 0018:a81802023908 EFLAGS: 00010286
  [  167.696027] RAX: ed8786e33a80 RBX: ed878c6d21b0 RCX: 
8000
  [  167.696027] RDX:  RSI: 3000 RDI: 
8001b8cea225
  [  167.696028] RBP: a81802023970 R08: 8001b8cea225 R09: 
90c4d55fa340
  [  167.696028] R10:  R11:  R12: 
ed8786e33a80
  [  167.696029] R13: 0326 R14: 90c4db94fc50 R15: 
90c4d55fa340
  [  167.696030] FS:  7f6a7798c700() GS:90c4edc8() 
knlGS:
  [  167.696030] CS:  0010 DS:  ES:  CR0: 80050033
  [  167.696031] CR2:  CR3: 000315580002 CR4: 
00162ee0
  [  167.696033] Call Trace:
  [  167.696047]  follow_pmd_mask+0x273/0x630
  [  167.696049]  follow_page_mask+0x178/0x230
  [  167.696051]  __get_user_pages+0xb8/0x740
  [  167.696052]  get_user_pages+0x42/0x50
  [  167.696068]  __gfn_to_pfn_memslot+0x18b/0x3b0 [kvm]
  [  167.696079]  ? mmu_set_spte+0x1dd/0x3a0 [kvm]
  [  167.696090]  try_async_pf+0x66/0x220 [kvm]
  [  167.696101]  tdp_page_fault+0x14b/0x2b0 [kvm]
  [  167.696104]  ? vmexit_fill_RSB+0x10/0x40 [kvm_intel]
  [  167.696114]  kvm_mmu_page_fault+0x62/0x180 [kvm]
  [  167.696117]  handle_ept_violation+0xbc/0x160 [kvm_intel]
  [  167.696119]  vmx_handle_exit+0xa5/0x580 [kvm_intel]
  [  167.696129]  vcpu_enter_guest+0x414/0x1260 [kvm]
  [  167.696138]  ? kvm_arch_vcpu_load+0x4d/0x280 [kvm]
  [  167.696148]  kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm]
  [  167.696157]  ? kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm]
  [  167.696165]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
  [  167.696166]  ? do_futex+0x129/0x590
  [  167.696171]  ?

[Kernel-packages] [Bug 1837810] Re: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host

Attached is a script to create and destroy VMs in a loop, to try and
increment the zero_page reference counter.

** Attachment added: "Reproducer script to create and destroy VMs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837810/+attachment/5402013/+files/ksm_refcnt_overflow.sh

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

Title:
  KVM: Fix zero_page reference counter overflow when using KSM on KVM
  compute host

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1837810

  [Impact]

  We are seeing a problem on OpenStack compute nodes, and KVM hosts,
  where a kernel oops is generated, and all running KVM machines are
  placed into the pause state.

  This is caused by the kernel's reserved zero_page reference counter
  overflowing from a positive number to a negative number, and hitting a
  (WARN_ON_ONCE(page_ref_count(page) <= 0)) condition in try_get_page().

  This only happens if the machine has Kernel Samepage Mapping (KSM)
  enabled, with "use_zero_pages" turned on. Each time a new VM starts
  and the kernel does a KSM merge run during a EPT violation, the
  reference counter for the zero_page is incremented in try_async_pf()
  and never decremented. Eventually, the reference counter will
  overflow, causing the KVM subsystem to fail.

  Syslog:
  error : qemuMonitorJSONCheckError:392 : internal error: unable to execute 
QEMU command 'cont': Resetting the Virtual Machine is required

  QEMU Logs:
  error: kvm run failed Bad address
  EAX=000afe00 EBX=000b ECX=0080 EDX=0cfe
  ESI=0003fe00 EDI=000afe00 EBP=0007 ESP=6d74
  EIP=000ee344 EFL=00010002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =0010   00c09300 DPL=0 DS   [-WA]
  CS =0008   00c09b00 DPL=0 CS32 [-RA]
  SS =0010   00c09300 DPL=0 DS   [-WA]
  DS =0010   00c09300 DPL=0 DS   [-WA]
  FS =0010   00c09300 DPL=0 DS   [-WA]
  GS =0010   00c09300 DPL=0 DS   [-WA]
  LDT=   8200 DPL=0 LDT
  TR =   8b00 DPL=0 TSS32-busy
  GDT= 000f7040 0037
  IDT= 000f707e 
  CR0=0011 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=c3 57 56 b8 00 fe 0a 00 be 00 fe 03 00 b9 80 00 00 00 89 c7  a5 a1 
00 80 03 00 8b 15 04 80 03 00 a3 00 80 0a 00 89 15 04 80 0a 00 b8 ae e2 00 00 31

  Kernel Oops:

  [  167.695986] WARNING: CPU: 1 PID: 3016 at 
/build/linux-hwe-FEhT7y/linux-hwe-4.15.0/include/linux/mm.h:852 
follow_page_pte+0x6f4/0x710
  [  167.696023] CPU: 1 PID: 3016 Comm: CPU 0/KVM Tainted: G   OE
4.15.0-106-generic #107~16.04.1-Ubuntu
  [  167.696023] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.13.0-1ubuntu1 04/01/2014
  [  167.696025] RIP: 0010:follow_page_pte+0x6f4/0x710
  [  167.696026] RSP: 0018:a81802023908 EFLAGS: 00010286
  [  167.696027] RAX: ed8786e33a80 RBX: ed878c6d21b0 RCX: 
8000
  [  167.696027] RDX:  RSI: 3000 RDI: 
8001b8cea225
  [  167.696028] RBP: a81802023970 R08: 8001b8cea225 R09: 
90c4d55fa340
  [  167.696028] R10:  R11:  R12: 
ed8786e33a80
  [  167.696029] R13: 0326 R14: 90c4db94fc50 R15: 
90c4d55fa340
  [  167.696030] FS:  7f6a7798c700() GS:90c4edc8() 
knlGS:
  [  167.696030] CS:  0010 DS:  ES:  CR0: 80050033
  [  167.696031] CR2:  CR3: 000315580002 CR4: 
00162ee0
  [  167.696033] Call Trace:
  [  167.696047]  follow_pmd_mask+0x273/0x630
  [  167.696049]  follow_page_mask+0x178/0x230
  [  167.696051]  __get_user_pages+0xb8/0x740
  [  167.696052]  get_user_pages+0x42/0x50
  [  167.696068]  __gfn_to_pfn_memslot+0x18b/0x3b0 [kvm]
  [  167.696079]  ? mmu_set_spte+0x1dd/0x3a0 [kvm]
  [  167.696090]  try_async_pf+0x66/0x220 [kvm]
  [  167.696101]  tdp_page_fault+0x14b/0x2b0 [kvm]
  [  167.696104]  ? vmexit_fill_RSB+0x10/0x40 [kvm_intel]
  [  167.696114]  kvm_mmu_page_fault+0x62/0x180 [kvm]
  [  167.696117]  handle_ept_violation+0xbc/0x160 [kvm_intel]
  [  167.696119]  vmx_handle_exit+0xa5/0x580 [kvm_intel]
  [  167.696129]  vcpu_enter_guest+0x414/0x1260 [kvm]
  [  167.696138]  ? kvm_arch_vcpu_load+0x4d/0x280 [kvm]
  [  167.696148]  kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm]
  [  167.696157]  ? kvm_arch_vcpu_ioctl_run+0xd9/0x3d0 [kvm]
  [  167.696165]  kvm_vcpu_ioctl+0x33a/0x610 [kvm]
  [  167.696166]  ? do_futex+0x129/0x590
  [  167.696171]  ? __switch_to+0x34c/0x4e0
  [  167.696174]

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-08-16 Thread Stefano Galassi

hehe no worries.. I was thinking someone was trying to prematurely close
the issue ;)

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion:

[Kernel-packages] [Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD

2020-08-16 Thread nyarla33

I tested my wifi with *** iwd *** instead of *** wpa_supplicant***, following
this "Call for testing: improved WiFi via iwd":
https://discourse.ubuntu.com/t/call-for-testing-improved-wifi-via-iwd/17795

When connected on the 5 GHz network, when the channel switches, syslog
and kern.log no longer grow endlessly. Connection is lost and that's
all.

** Attachment added: "syslog part"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+attachment/5401977/+files/syslog%20part

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

Title:
Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel
switch, iwlwifi Microcode SW Error: FW error in SYNC CMD
CHANNEL_SWITCH_TIME_EVENT_CMD

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33

I occasionally see a message on my screen that disk space is low. I
try rebooting since my computer is unresponsive. Normal reboot does
not work, sudo reboot does not work. I have to power off the machine
using power button. Machine boots but hangs because its trying to
repair journal info.

I can't see what causes that since I was not using my computer at the time.
edit: see comment #14

So with a live session, I can see that syslog and kern.log files have
grown to several GB until the drive is full.

When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any
problem so far.
edit: not true actually, this happened again using this upstream kernel.

Never had this issue with previous Ubuntu versions with the very same
hardware configuration, since 16.04.

Included: partial syslog and kern.log with the same message repeated over and
over.
edit: and when the event starts.

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2020-08-16 Thread Luis A

This bug still affect the install process today, with ubuntu 20.04 LTS
and same with kubuntu installer.

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  WORKAROUND: add pci=noaer to your kernel command line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

2020-08-16 Thread Hoyong Hwang

Mine isn't Thinkbook though, #7 solved my problem on ideapad s145.
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/1885573

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: Elan
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode

2020-08-16 Thread Luc Stroobant

I'm also affected by this bug on a Lenovo X395 and can confirm the
workaround in #20 works.

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

Title:
  [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad
  L340-17API when in battery mode

Status in linux package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Xubuntu 20.04 shows black screen instead of login
  screen upon boot on Lenovo Ideapad L340-17API. It is not possible to
  chvt to text terminal when boot is stuck on black screen.

  Booting with 'nomodeset' kernel option works properly but is not an
  option (e.g. screen brightness is not adjustable in this case).

  Another workaround is to ssh to laptop and run systemctl restart
  display-manager.service. After 5-10 seconds upon executing this
  command perfectly working login screen appears.

  Check dmesg. There is apparently related messages from amdgpu driver:

  ...
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done
  апр 05 20:46:45 kernel: [drm] Skip scheduling IBs!
  апр 05 20:46:45 kernel: [ cut here ]
  апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at 
include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched]
  апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher 
af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec >
  апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G  
 OE 5.4.0-21-generic #25-Ubuntu
  апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 
07/11/2019
  апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched]
  апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 
[gpu_sched]
  апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 
48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf 
<0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c
  апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246
  апр 05 20:46:45 kernel: RAX:  RBX: 0001 RCX: 

  апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: 

  апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 
0004
  апр 05 20:46:45 kernel: R10:  R11: 0001 R12: 
8cc9ac463c00
  апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 
8cc9a6fc9140
  апр 05 20:46:45 kernel: FS:  () GS:8cc9b88c() 
knlGS:
  апр 05 20:46:45 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 
003406e0
  апр 05 20:46:45 kernel: Call Trace:
  апр 05 20:46:45 kernel:  amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu]
  апр 05 20:46:45 kernel:  amdgpu_job_timedout+0x103/0x130 [amdgpu]
  апр 05 20:46:45 kernel:  drm_sched_job_timedout+0x44/0x90 [gpu_sched]
  апр 05 20:46:45 kernel:

[Kernel-packages] [Bug 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other

2020-08-16 Thread Simon Arlott

I'm also getting kcompactd0 hanging on its own on another host, which 
presumably blocks btrfs-transaction later on:
[606364.285752] INFO: task kcompactd0:27 blocked for more than 120 seconds.
[606364.285994]   Not tainted 4.15.0-112-generic #113-Ubuntu
[606364.286129] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[606364.286268] kcompactd0  D027  2 0x8000
[606364.286270] Call Trace:
[606364.286284]  __schedule+0x24e/0x880
[606364.286341]  ? btree_releasepage+0x42/0x50 [btrfs]
[606364.286343]  schedule+0x2c/0x80
[606364.286344]  io_schedule+0x16/0x40
[606364.286345]  __lock_page+0xff/0x140
[606364.286347]  ? page_cache_tree_insert+0xe0/0xe0
[606364.286348]  migrate_pages+0x91f/0xb80
[606364.286349]  ? __ClearPageMovable+0x10/0x10
[606364.286350]  ? isolate_freepages_block+0x3b0/0x3b0
[606364.286351]  compact_zone+0x681/0x950
[606364.286352]  kcompactd_do_work+0xfe/0x2a0
[606364.286354]  ? __switch_to_asm+0x35/0x70
[606364.286355]  ? __switch_to_asm+0x41/0x70
[606364.286356]  kcompactd+0x86/0x1c0
[606364.286357]  ? kcompactd+0x86/0x1c0
[606364.286358]  ? wait_woken+0x80/0x80
[606364.286360]  kthread+0x121/0x140
[606364.286361]  ? kcompactd_do_work+0x2a0/0x2a0
[606364.286361]  ? kthread_create_worker_on_cpu+0x70/0x70
[606364.286363]  ret_from_fork+0x35/0x40

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

Title:
  kcompactd0 and btrfs-transaction keep deadlocking with each other

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Example 1:
  [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds.
  [346911.187938]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.187968] kcompactd0  D053  2 0x8000
  [346911.187969] Call Trace:
  [346911.187973]  __schedule+0x24e/0x880
  [346911.187986]  ? btree_releasepage+0x42/0x50 [btrfs]
  [346911.187987]  schedule+0x2c/0x80
  [346911.187988]  io_schedule+0x16/0x40
  [346911.187989]  __lock_page+0xff/0x140
  [346911.187990]  ? page_cache_tree_insert+0xe0/0xe0
  [346911.187992]  migrate_pages+0x91f/0xb80
  [346911.187993]  ? __ClearPageMovable+0x10/0x10
  [346911.187994]  ? isolate_freepages_block+0x3b0/0x3b0
  [346911.187995]  compact_zone+0x681/0x950
  [346911.187995]  kcompactd_do_work+0xfe/0x2a0
  [346911.187996]  ? __switch_to_asm+0x35/0x70
  [346911.187997]  ? __switch_to_asm+0x41/0x70
  [346911.187998]  kcompactd+0x86/0x1c0
  [346911.187999]  ? kcompactd+0x86/0x1c0
  [346911.188001]  ? wait_woken+0x80/0x80
  [346911.188002]  kthread+0x121/0x140
  [346911.188003]  ? kcompactd_do_work+0x2a0/0x2a0
  [346911.188003]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188004]  ret_from_fork+0x35/0x40

  [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 
seconds.
  [346911.188031]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.188060] btrfs-transacti D0   858  2 0x8000
  [346911.188061] Call Trace:
  [346911.188062]  __schedule+0x24e/0x880
  [346911.188063]  ? bit_wait+0x60/0x60
  [346911.188063]  schedule+0x2c/0x80
  [346911.188064]  io_schedule+0x16/0x40
  [346911.188065]  bit_wait_io+0x11/0x60
  [346911.188066]  __wait_on_bit+0x4c/0x90
  [346911.188066]  ? bit_wait+0x60/0x60
  [346911.188067]  out_of_line_wait_on_bit+0x90/0xb0
  [346911.188068]  ? bit_waitqueue+0x40/0x40
  [346911.188080]  lock_extent_buffer_for_io+0x100/0x2a0 [btrfs]
  [346911.188090]  btree_write_cache_pages+0x1b8/0x420 [btrfs]
  [346911.188092]  ? native_sched_clock_from_tsc+0x30/0x70
  [346911.188092]  ? update_load_avg+0x423/0x780
  [346911.188101]  btree_writepages+0x5d/0x70 [btrfs]
  [346911.188102]  do_writepages+0x4b/0xe0
  [346911.188102]  ? enqueue_task_fair+0xb6/0x300
  [346911.188111]  ? merge_state.part.47+0x44/0x130 [btrfs]
  [346911.188112]  __filemap_fdatawrite_range+0xcf/0x100
  [346911.188113]  ? __filemap_fdatawrite_range+0xcf/0x100
  [346911.188114]  filemap_fdatawrite_range+0x13/0x20
  [346911.188122]  btrfs_write_marked_extents+0x68/0x140 [btrfs]
  [346911.188129]  btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 
[btrfs]
  [346911.188136]  btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188143]  ? btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188144]  ? wait_woken+0x80/0x80
  [346911.188151]  transaction_kthread+0x18d/0x1b0 [btrfs]
  [346911.188152]  kthread+0x121/0x140
  [346911.188158]  ? btrfs_cleanup_transaction+0x570/0x570 [btrfs]
  [346911.188159]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188160]  ret_from_fork+0x35/0x40

  Example 2:
  2020-08-11T20:23:03.533+01:00  kernel: INFO: task kcompactd0:53 blocked 
for more than 120 seconds.
  2020-08-11T20:23:03.533+01:00  kernel:

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

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

Title:
  doesnt recognize the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  cat /proc/bus/input/devices doesnt show touchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thiago 1569 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 13:41:16 2020
  InstallationDate: Installed on 2020-08-15 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp1s0f0  no wireless extensions.
   
   usb0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. Macmini6,1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1b99b69-6ce5-4c95-80ca-69c1e70dff35 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 286.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031AEE4D24BFF0B1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini6,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-031AEE4D24BFF0B1
  dmi.modalias: 
dmi:bvnAppleInc.:bvr286.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacmini6,1:pvr1.0:rvnAppleInc.:rnMac-031AEE4D24BFF0B1:rvrMacmini6,1:cvnAppleInc.:ct16:cvrMac-031AEE4D24BFF0B1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini6,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1891811] [NEW] doesnt recognize the trackpad

2020-08-16 Thread Thiago de Oliveira Barbosa

Public bug reported:

cat /proc/bus/input/devices doesnt show touchpad

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
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.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  thiago 1569 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 16 13:41:16 2020
InstallationDate: Installed on 2020-08-15 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
 enp1s0f0  no wireless extensions.
 
 usb0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Apple Inc. Macmini6,1
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1b99b69-6ce5-4c95-80ca-69c1e70dff35 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.2
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 286.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-031AEE4D24BFF0B1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini6,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-031AEE4D24BFF0B1
dmi.modalias: 
dmi:bvnAppleInc.:bvr286.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacmini6,1:pvr1.0:rvnAppleInc.:rnMac-031AEE4D24BFF0B1:rvrMacmini6,1:cvnAppleInc.:ct16:cvrMac-031AEE4D24BFF0B1:
dmi.product.family: Macmini
dmi.product.name: Macmini6,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  doesnt recognize the trackpad

Status in linux package in Ubuntu:
  New

Bug description:
  cat /proc/bus/input/devices doesnt show touchpad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thiago 1569 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 13:41:16 2020
  InstallationDate: Installed on 2020-08-15 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp1s0f0  no wireless extensions.
   
   usb0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. Macmini6,1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1b99b69-6ce5-4c95-80ca-69c1e70dff35 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 286.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031AEE4D24BFF0B1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini6,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-031AEE4D24BFF0B1
  dmi.modalias: 
dmi:bvnAppleInc.:bvr286.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacmini6,1:pvr1.0:rvnAppleInc.:rnMac-031AEE4D24BFF0B1:rvrMacmini6,1:cvnAppleInc.:ct16:cvrMac-031AEE4D24BFF0B1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini6,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1779007] Re: BUG - vboxdrv.sh - failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

2020-08-16 Thread Ramone Burrell

Thank you, Joseph Salisbury.

I was struggling with this issue for hours but solved it once I upgraded
to a later kernel version.

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

Title:
  BUG - vboxdrv.sh - failed: modprobe vboxdrv failed. Please use 'dmesg'
  to find out why.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  romulorafa@romulorafa:~$ virtualbox virtualbox/delete-old-modules boolean true
  WARNING: The vboxdrv kernel module is not loaded. Either there is no module
   available for the current kernel (4.15.0-23-generic) or it failed to
   load. Please recompile the kernel module and install it by

 sudo /sbin/vboxconfig

   You will not be able to start VMs until this problem is fixed.
  romulorafa@romulorafa:~$ sudo /sbin/vboxconfig
  vboxdrv.sh: Stopping VirtualBox services.
  vboxdrv.sh: Building VirtualBox kernel modules.
  vboxdrv.sh: Starting VirtualBox services.
  vboxdrv.sh: Building VirtualBox kernel modules.
  vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out 
why.

  There were problems setting up VirtualBox.  To re-start the set-up process, 
run
/sbin/vboxconfig
  as root.


  romulorafa@romulorafa:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  romulorafa@romulorafa:~$ cat /proc/version_signature
  Ubuntu 4.15.0-23.25-generic 4.15.18

  romulorafa@romulorafa:~$ sudo lspci -vnvn
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: Acer Incorporated [ALI] Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1193]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 
xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP USB 3.0 xHCI 
Controller [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21)
Subsystem: Acer Incorporated [ALI] Sunrise Point-LP Serial IO I2C 
Controller [1025:1193]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel

[Kernel-packages] [Bug 1890796] Re: ipsec: policy priority management is broken

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  ipsec: policy priority management is broken

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-hwe source package in Xenial:
  Invalid
Status in linux-oem-5.6 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe source package in Focal:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  Confirmed

Bug description:
  [Impact]

  When the user tries to update the priority field of a SP, the SP is
  not updated *AND* a new SP is created. This results to a broken IPsec
  configuration.

  This problem has been fixed in the upstream commit 4f47e8ab6ab7 ("xfrm: 
policy: match with both mark and mask on user interfaces"):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f47e8ab6ab7

  [Test Case]

  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~# ip xfrm policy flush
  root@dut-vm:~# ip xfrm policy
  root@dut-vm:~# ip xfrm policy add src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp dir 
in action allow priority 9 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel 
reqid 1
  root@dut-vm:~# ip xfrm policy
  src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
  dir in priority 9 
  tmpl src 3.3.3.3 dst 4.4.4.4
  proto esp reqid 1 mode tunnel
  root@dut-vm:~# ip xfrm policy update src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
dir in priority 5 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel reqid 1
  root@dut-vm:~# ip xfrm policy
  src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
  dir in priority 5 
  tmpl src 3.3.3.3 dst 4.4.4.4
  proto esp reqid 1 mode tunnel
  src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp 
  dir in priority 9 
  tmpl src 3.3.3.3 dst 4.4.4.4
  proto esp reqid 1 mode tunnel
  root@dut-vm:~#

  => Now, there is 2 SP instead of 1.

  [Regression Potential]

  The patch affects the xfrm stack only. Thus, the potential regressions
  are limited to this area.

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

-- 
Mailing list: https://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

2020-08-16 Thread Anupam Jayaraj

I think the Ubuntu kernel gpu drivers are below average.Trying amd gpu pro
driver is better option.Ubuntu shall study a lot of things from amd gpu
pro

On Aug 14, 2020 5:22 PM, "Anupam Jayaraj"  wrote:

> 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.20200
>>> 8111432_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

[Kernel-packages] [Bug 1803179]

2020-08-16 Thread xxxaaa

(In reply to Karol Herbst from comment #169)
> (In reply to xxxaaa from comment #168)
> > (In reply to Karol Herbst from comment #167)
> > > btw, this bug should be fixed with the nouveau river in 5.7 (and
> backports
> > > should follow soon for 5.4, 5.5 and 5.6)
> > 
> > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 but
> > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it
> > work only for nouveau drivers?
> 
> the fix is for Nouveau only, but I am actually in contact with Nvidia about
> the same issue they have inside their driver as well.
> 
> But the bug can be fixed from within the open source files inside the nvidia
> driver as well I just hope that Nvidia will have a proper solution here as
> the fix in Nouveau is also more of a workaround than a real fix.

(Sorry for being impatient but this bug has been bugging me a lot.)
Do you know if this has been fixed on Nvidia Drivers yet or not? And if it has 
not been fixed then whether it is on their roadmap or not?

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1803179]

2020-08-16 Thread karolherbst

(In reply to xxxaaa from comment #173)
> (In reply to Karol Herbst from comment #169)
> > (In reply to xxxaaa from comment #168)
> > > (In reply to Karol Herbst from comment #167)
> > > > btw, this bug should be fixed with the nouveau river in 5.7 (and
> > backports
> > > > should follow soon for 5.4, 5.5 and 5.6)
> > > 
> > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727
> but
> > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it
> > > work only for nouveau drivers?
> > 
> > the fix is for Nouveau only, but I am actually in contact with Nvidia about
> > the same issue they have inside their driver as well.
> > 
> > But the bug can be fixed from within the open source files inside the
> nvidia
> > driver as well I just hope that Nvidia will have a proper solution here as
> > the fix in Nouveau is also more of a workaround than a real fix.
> 
> (Sorry for being impatient but this bug has been bugging me a lot.)
> Do you know if this has been fixed on Nvidia Drivers yet or not? And if it
> has not been fixed then whether it is on their roadmap or not?

Afaik they do not and my attempts to get them to even reproduce the
issue failed...

so I don't see it getting fixed any time soon and honestly, if I have to
put more time into it I might even stop caring as the fix we have for
Nouveau is good enough and appears to have resolved the issue for good.

In case you are still plagued by it I suspect you might want to bring
that up to Nvidia directly and see if they get more motivated fixing it
if they get more reports.

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1803179]

2020-08-16 Thread xxxaaa

(In reply to Karol Herbst from comment #174)
> (In reply to xxxaaa from comment #173)
> > (In reply to Karol Herbst from comment #169)
> > > (In reply to xxxaaa from comment #168)
> > > > (In reply to Karol Herbst from comment #167)
> > > > > btw, this bug should be fixed with the nouveau river in 5.7 (and
> > > backports
> > > > > should follow soon for 5.4, 5.5 and 5.6)
> > > > 
> > > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727
> > but
> > > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does
> it
> > > > work only for nouveau drivers?
> > > 
> > > the fix is for Nouveau only, but I am actually in contact with Nvidia
> about
> > > the same issue they have inside their driver as well.
> > > 
> > > But the bug can be fixed from within the open source files inside the
> > nvidia
> > > driver as well I just hope that Nvidia will have a proper solution here
> as
> > > the fix in Nouveau is also more of a workaround than a real fix.
> > 
> > (Sorry for being impatient but this bug has been bugging me a lot.)
> > Do you know if this has been fixed on Nvidia Drivers yet or not? And if it
> > has not been fixed then whether it is on their roadmap or not?
> 
> Afaik they do not and my attempts to get them to even reproduce the issue
> failed...
> 
> so I don't see it getting fixed any time soon and honestly, if I have to put
> more time into it I might even stop caring as the fix we have for Nouveau is
> good enough and appears to have resolved the issue for good.
> 
> In case you are still plagued by it I suspect you might want to bring that
> up to Nvidia directly and see if they get more motivated fixing it if they
> get more reports.

I had asked about it in the nvidia linux forums some time back but nothing came 
out of it either :(
https://forums.developer.nvidia.com/t/bug-cant-change-power-state-from-d3cold-to-d0-config-space-inaccessible-stuck-at-boot/112912
 

Some time back you had said -

> But the bug can be fixed from within the open source files inside the nvidia
> driver

So, can your nouveau patch be applied to nvidia driver as well?

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-08-16 Thread Maton Danko

I've added wrong distro and when I'm removed it from the list it created
that comment automatically. This interface not too intuitive for me.
Sorry.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor:

[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT

2020-08-16 Thread Sergey Kostyuk

Hello Kai-Heng Feng,

Please find my report below. Let me know if you need any additional
information.

Environment:
- Device Model: ASUS Zenbook UX534FTC-A8101T.
- BIOS: Version 305 2020/04/13
- Test Case: Cold boot to Ubuntu 20.04, kernel from comment #184 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/184). No 
workaround commands executed.
- Test application: Firefox, Audacity

Test results:
- Speakers: Work, no distortions.
- Headphones (w/o microphone): Work, no distortions.
- Internal mic: Works, no distortions.
- Headset mic: Works, no distortions.
- Headset detection (switching from internal to external mic): Works perfectly
- Headphone detection (switching from internal speakers): Works perfectly

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

Title:
  No sound on ASUS UX534FT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  after instal Ubuntu in dual boot alongside Windows 10, I've realised
  there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
  AA024R in Ubuntu. In Windows there is no problem. Found this topic
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
  the same problem with driver for Realtek ALC294 which is also mine
  sound card. But even with this fix it is not working on UX534FT. Can
  you please add fix also for this newer model?

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
  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.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 29 15:11:25 2019
  InstallationDate: Installed on 2019-10-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-08-16 Thread Stefano Galassi

what does it means "no longer affects: linux"?
in mine and many others cases it does still affect linux and no valid solutions 
to this issue have been found to date

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-08-16 Thread Stefano Galassi

what does it means "no longer affects: linux"?
in my and many others cases it does still affects linux and now valid solution 
to this issue has been found to date

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05

[Kernel-packages] [Bug 1891790] Re: lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4 kernel only)

FYI:  I could run `apport-collect` on either box using Lubuntu 18.04.4
ISO, or earlier ISO, but I've really tried using 18.04.5 & neither
laptop is usable on those boxes (likely two issues, laptop screen
unreadable & it slows & freezes due a possibly different issue; this is
the real killed as I haven't been able to authorize upload)

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

Title:
  lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4
  kernel only)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ** Summary
  Screen is unreadable much of the time with black badly-tuned-digital-tv type 
fragments covering image. As you action things (use a menu, click on a 
different window etc) the black fragments move (though often only parts of 
screen; not all of screen)

  ** Background

  This was looked into because of a number of support requests and I
  detected a pattern.  All users are using the HWE kernel, and issue
  didn't occur using 18.04.4, though I personally only tested the live
  daily (during the development cycle).

  - thinkpad x31
  
https://discourse.lubuntu.me/t/reviving-thinkpad-x31-problems-with-messed-up-screen/1457/
  - thinkpad t42
  https://ubuntuforums.org/showthread.php?t=2448800=13979514#post13979514
  - thinkpad t41
  
https://askubuntu.com/questions/1266918/latest-updates-to-lubuntu-18-04-4-lts-32-bit-create-almost-impossible-graphics-i

  (and I believe others before I recognized the pattern & started
  noting; I ignored initially as I had no issues with t43, not having
  used the t42p or r50p in QA testing for awhile - a scan of my QA-
  testing live will show when I tested with each box in first line of
  comments).  I've also seen this on very different boxes to old
  thinkpads too.

  My boxes impacted

  - ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)
  - ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)

  ** 20.04/HWE kernel only

  If I live QA-test using the 18.04.4 ISO or released image, no issues
  occur (using 5.3 kernel & it's packages).  Likewise I have no issues
  using the GA (4.15) kernel in testing (the r50p was used more
  regularly in testing in prior bionic cycles, alas not much in 18.04.5
  development/recently; expecting same results with thinkpad t43 which
  does not have this issue)

  This report should possibly be filed on xserver-xorg. I've only
  experienced it with old radeon thinkpads (but screen on box makes it
  difficult to explore)

  (Filed online as I've been struggling to file this on actual box)

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

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

[Kernel-packages] [Bug 1891790] Re: lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4 kernel only)

I doubt I'm going to be able to `apport-collect 1891790` as I tried for
>3 hours on the r50p, and the t42p is now having the same issue (it's
just slower to be impacted; maybe because it has more RAM)

Checks for squashfs errors are clean (ie. `dmesg|grep squash`) with only
program title appearing once, no errors

Both boxes crash though, at first slow to respond till the eventually
pause.  If I try `ubuntu-bug linux` (last done on t42p) I get a crash
file in /var/crash, but it's hard to read, and it won't file using
`ubuntu-bug`.

The closest I got was authorization is required, but firefox never gets
to show anything allowing me to authorize it. The laptops appear to get
slower & slower they run, and trying to read anything useful on the
screen isn't really possible.

I even tried `sudo apt install openssh-server` hoping I could read more
from a different box, but that seems to speed up the slowing nature of
whatever this box doesn't like in the 5.4 kernel/stack.  This will
likely be a different issue, but why I filed on the kernel, not xserver-
xorg

(apport-collect has now run >30 mins on t42p and I've not been able to
authorize it, can't move mouse anymore, but I'm giving up... SysRq
caused reboot, so kernel is still running, even if I could not use
ctrl+alt+f4 to switch to text terminal; fyi: text terminals are easily
read)

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

Title:
  lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4
  kernel only)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ** Summary
  Screen is unreadable much of the time with black badly-tuned-digital-tv type 
fragments covering image. As you action things (use a menu, click on a 
different window etc) the black fragments move (though often only parts of 
screen; not all of screen)

  ** Background

  This was looked into because of a number of support requests and I
  detected a pattern.  All users are using the HWE kernel, and issue
  didn't occur using 18.04.4, though I personally only tested the live
  daily (during the development cycle).

  - thinkpad x31
  
https://discourse.lubuntu.me/t/reviving-thinkpad-x31-problems-with-messed-up-screen/1457/
  - thinkpad t42
  https://ubuntuforums.org/showthread.php?t=2448800=13979514#post13979514
  - thinkpad t41
  
https://askubuntu.com/questions/1266918/latest-updates-to-lubuntu-18-04-4-lts-32-bit-create-almost-impossible-graphics-i

  (and I believe others before I recognized the pattern & started
  noting; I ignored initially as I had no issues with t43, not having
  used the t42p or r50p in QA testing for awhile - a scan of my QA-
  testing live will show when I tested with each box in first line of
  comments).  I've also seen this on very different boxes to old
  thinkpads too.

  My boxes impacted

  - ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)
  - ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)

  ** 20.04/HWE kernel only

  If I live QA-test using the 18.04.4 ISO or released image, no issues
  occur (using 5.3 kernel & it's packages).  Likewise I have no issues
  using the GA (4.15) kernel in testing (the r50p was used more
  regularly in testing in prior bionic cycles, alas not much in 18.04.5
  development/recently; expecting same results with thinkpad t43 which
  does not have this issue)

  This report should possibly be filed on xserver-xorg. I've only
  experienced it with old radeon thinkpads (but screen on box makes it
  difficult to explore)

  (Filed online as I've been struggling to file this on actual box)

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

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

[Kernel-packages] [Bug 1891790] Re: lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4 kernel only)

Photo of live (Lubuntu 18.04.5) running on r50p

ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2;
rv350/m10 gl)

https://photos.google.com/share/AF1QipMVvJkfURew9B14g4-wmVSUoPMmwjrWCBY1GS9ZDxTa_NPvEwJTEngUnnZAOmsqkQ/photo
/AF1QipMtgzUJJE3mZ4IdUXWAW4_UNB7SH3hCPlt-
XbEr?key=dkU2T2c0WUJzVi1xNVI3cURUTG9TZlJyYnNNSnFn


Photo of live (Lubuntu 18.04.5) running on t42p

ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2;
rv350/m10 gl)

https://photos.google.com/share/AF1QipMVvJkfURew9B14g4-wmVSUoPMmwjrWCBY1GS9ZDxTa_NPvEwJTEngUnnZAOmsqkQ/photo/AF1QipMXR61U1xJK6gzkoKoatHXgUcok8_8ZgxghKtYv?key=dkU2T2c0WUJzVi1xNVI3cURUTG9TZlJyYnNNSnFn

** Tags added: bionic i386

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

Title:
  lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4
  kernel only)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ** Summary
  Screen is unreadable much of the time with black badly-tuned-digital-tv type 
fragments covering image. As you action things (use a menu, click on a 
different window etc) the black fragments move (though often only parts of 
screen; not all of screen)

  ** Background

  This was looked into because of a number of support requests and I
  detected a pattern.  All users are using the HWE kernel, and issue
  didn't occur using 18.04.4, though I personally only tested the live
  daily (during the development cycle).

  - thinkpad x31
  
https://discourse.lubuntu.me/t/reviving-thinkpad-x31-problems-with-messed-up-screen/1457/
  - thinkpad t42
  https://ubuntuforums.org/showthread.php?t=2448800=13979514#post13979514
  - thinkpad t41
  
https://askubuntu.com/questions/1266918/latest-updates-to-lubuntu-18-04-4-lts-32-bit-create-almost-impossible-graphics-i

  (and I believe others before I recognized the pattern & started
  noting; I ignored initially as I had no issues with t43, not having
  used the t42p or r50p in QA testing for awhile - a scan of my QA-
  testing live will show when I tested with each box in first line of
  comments).  I've also seen this on very different boxes to old
  thinkpads too.

  My boxes impacted

  - ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)
  - ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)

  ** 20.04/HWE kernel only

  If I live QA-test using the 18.04.4 ISO or released image, no issues
  occur (using 5.3 kernel & it's packages).  Likewise I have no issues
  using the GA (4.15) kernel in testing (the r50p was used more
  regularly in testing in prior bionic cycles, alas not much in 18.04.5
  development/recently; expecting same results with thinkpad t43 which
  does not have this issue)

  This report should possibly be filed on xserver-xorg. I've only
  experienced it with old radeon thinkpads (but screen on box makes it
  difficult to explore)

  (Filed online as I've been struggling to file this on actual box)

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

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

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

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 1891790

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

Title:
  lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4
  kernel only)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ** Summary
  Screen is unreadable much of the time with black badly-tuned-digital-tv type 
fragments covering image. As you action things (use a menu, click on a 
different window etc) the black fragments move (though often only parts of 
screen; not all of screen)

  ** Background

  This was looked into because of a number of support requests and I
  detected a pattern.  All users are using the HWE kernel, and issue
  didn't occur using 18.04.4, though I personally only tested the live
  daily (during the development cycle).

  - thinkpad x31
  
https://discourse.lubuntu.me/t/reviving-thinkpad-x31-problems-with-messed-up-screen/1457/
  - thinkpad t42
  https://ubuntuforums.org/showthread.php?t=2448800=13979514#post13979514
  - thinkpad t41
  
https://askubuntu.com/questions/1266918/latest-updates-to-lubuntu-18-04-4-lts-32-bit-create-almost-impossible-graphics-i

  (and I believe others before I recognized the pattern & started
  noting; I ignored initially as I had no issues with t43, not having
  used the t42p or r50p in QA testing for awhile - a scan of my QA-
  testing live will show when I tested with each box in first line of
  comments).  I've also seen this on very different boxes to old
  thinkpads too.

  My boxes impacted

  - ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)
  - ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)

  ** 20.04/HWE kernel only

  If I live QA-test using the 18.04.4 ISO or released image, no issues
  occur (using 5.3 kernel & it's packages).  Likewise I have no issues
  using the GA (4.15) kernel in testing (the r50p was used more
  regularly in testing in prior bionic cycles, alas not much in 18.04.5
  development/recently; expecting same results with thinkpad t43 which
  does not have this issue)

  This report should possibly be filed on xserver-xorg. I've only
  experienced it with old radeon thinkpads (but screen on box makes it
  difficult to explore)

  (Filed online as I've been struggling to file this on actual box)

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

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

[Kernel-packages] [Bug 1891790] [NEW] lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4 kernel only)

Public bug reported:

** Summary
Screen is unreadable much of the time with black badly-tuned-digital-tv type 
fragments covering image. As you action things (use a menu, click on a 
different window etc) the black fragments move (though often only parts of 
screen; not all of screen)

** Background

This was looked into because of a number of support requests and I
detected a pattern.  All users are using the HWE kernel, and issue
didn't occur using 18.04.4, though I personally only tested the live
daily (during the development cycle).

- thinkpad x31
https://discourse.lubuntu.me/t/reviving-thinkpad-x31-problems-with-messed-up-screen/1457/
- thinkpad t42
https://ubuntuforums.org/showthread.php?t=2448800=13979514#post13979514
- thinkpad t41
https://askubuntu.com/questions/1266918/latest-updates-to-lubuntu-18-04-4-lts-32-bit-create-almost-impossible-graphics-i

(and I believe others before I recognized the pattern & started noting;
I ignored initially as I had no issues with t43, not having used the
t42p or r50p in QA testing for awhile - a scan of my QA-testing live
will show when I tested with each box in first line of comments).  I've
also seen this on very different boxes to old thinkpads too.

My boxes impacted

- ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2; rv350/m10 
gl)
- ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2; rv350/m10 
gl)

** 20.04/HWE kernel only

If I live QA-test using the 18.04.4 ISO or released image, no issues
occur (using 5.3 kernel & it's packages).  Likewise I have no issues
using the GA (4.15) kernel in testing (the r50p was used more regularly
in testing in prior bionic cycles, alas not much in 18.04.5
development/recently; expecting same results with thinkpad t43 which
does not have this issue)

This report should possibly be filed on xserver-xorg. I've only
experienced it with old radeon thinkpads (but screen on box makes it
difficult to explore)

(Filed online as I've been struggling to file this on actual box)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1891790

Title:
  lubuntu 18.04.5 text unreadable on old thinkpads (radeon, HWE 5.4
  kernel only)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ** Summary
  Screen is unreadable much of the time with black badly-tuned-digital-tv type 
fragments covering image. As you action things (use a menu, click on a 
different window etc) the black fragments move (though often only parts of 
screen; not all of screen)

  ** Background

  This was looked into because of a number of support requests and I
  detected a pattern.  All users are using the HWE kernel, and issue
  didn't occur using 18.04.4, though I personally only tested the live
  daily (during the development cycle).

  - thinkpad x31
  
https://discourse.lubuntu.me/t/reviving-thinkpad-x31-problems-with-messed-up-screen/1457/
  - thinkpad t42
  https://ubuntuforums.org/showthread.php?t=2448800=13979514#post13979514
  - thinkpad t41
  
https://askubuntu.com/questions/1266918/latest-updates-to-lubuntu-18-04-4-lts-32-bit-create-almost-impossible-graphics-i

  (and I believe others before I recognized the pattern & started
  noting; I ignored initially as I had no issues with t43, not having
  used the t42p or r50p in QA testing for awhile - a scan of my QA-
  testing live will show when I tested with each box in first line of
  comments).  I've also seen this on very different boxes to old
  thinkpads too.

  My boxes impacted

  - ibm thinkpad t42p (pentium m, 2gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)
  - ibm thinkpad r50p (pentium m, 1gb ram, amd/ati mobility firegl t2; 
rv350/m10 gl)

  ** 20.04/HWE kernel only

  If I live QA-test using the 18.04.4 ISO or released image, no issues
  occur (using 5.3 kernel & it's packages).  Likewise I have no issues
  using the GA (4.15) kernel in testing (the r50p was used more
  regularly in testing in prior bionic cycles, alas not much in 18.04.5
  development/recently; expecting same results with thinkpad t43 which
  does not have this issue)

  This report should possibly be filed on xserver-xorg. I've only
  experienced it with old radeon thinkpads (but screen on box makes it
  difficult to explore)

  (Filed online as I've been struggling to file this on actual box)

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

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

[Kernel-packages] [Bug 1863958] Re: Bluez doesn't work well with Multipoint Audio Devices