[Kernel-packages] [Bug 2028933] Re: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)

2023-09-27 Thread Jaromir Obr
The same issue with:

* Dell Precision 7530, BIOS from 07/05/2023
* Nvidia Quadro P1000 Mobile
* Ubuntu 22.04.3 LTS
* linux-image-5.15.0-84-generic

dmesg logs many times this:
---
[Wed Sep 27 12:57:06 2023] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[Wed Sep 27 12:57:06 2023] ACPI Error: AE_ALREADY_EXISTS, During name 
lookup/catalog (20210730/psobject-220)
...

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

Title:
  ACPI BIOS Error (bug): Failure creating named object
  [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)

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

Bug description:
  At boot up after the GRUB selection, these ACPI BIOS Error (bug)
  appear.

  These errors were taken from dmesg but they report the similar error at boot 
up
  [0.320650] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320680] fbcon: Taking over console
  [0.320694] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320700] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320705] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320712] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320717] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320720] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320727] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320731] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320734] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320741] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320745] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320793] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320801] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320806] ACPI: Skipping parse of AML opcode: Method (0x0014)

  
  Then at runtime random Multiple Corrected error appear at this PCIe port
  1c.0-[01]00.0  Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 
M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]1c.0-[01]00.0  
Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]

  Not exactly connected but similar reports of ACPI error above is
  related to NVIDIA. Not sure if it helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-78-generic 5.15.0-78.85~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
  Uname: Linux 5.15.0-78-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 28 19:17:58 2023
  InstallationDate: Installed on 2021-08-15 (712 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2028933/+subscriptions


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


[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

2023-04-06 Thread Jaromir Obr
@pyabo I solved it by installation of kernel 6.2:
https://github.com/pimlie/ubuntu-mainline-kernel.sh. So far no other
issue appeared, I'm using Ubuntu 22.10.

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Triaged
Status in linux-oem-6.1 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

2023-03-24 Thread Jaromir Obr
Is there a chance to get a fix in Ubuntu 22.10 (with kernel 5.19)?

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Triaged
Status in linux-oem-6.1 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
  Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin!
  

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

2023-03-05 Thread Jaromir Obr
I just tried kernel 5.19.0-35-generic #36 on Ubuntu 22.10 (kinetic) that should 
contain the fix.
A few times when I suspend my notebook (Yoga Slim 7 14are05), the issue 
occurred with Slack (a snap app):

/var/log/syslog
---
Mar  5 20:33:27 rzbox ModemManager[1095]:   [sleep-monitor-systemd] 
system is about to suspend
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.6532] manager: 
sleep: sleep requested (sleeping: no  enabled: yes)
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.6533] device 
(eno1): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Mar  5 20:33:27 rzbox kernel: [ 2079.870212] audit: type=1107 
audit(1678044807.651:222): pid=998 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedes
ktop/login1" interface="org.freedesktop.login1.Manager" 
member="PrepareForSleep" name=":1.4" mask="receive" pid=6112 
label="snap.slack.slack" peer_pid=1033 peer_label="unconfined"
Mar  5 20:33:27 rzbox kernel: [ 2079.870212]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
Mar  5 20:33:27 rzbox google-chrome.desktop[4369]: 
[4363:4392:0305/203327.655811:ERROR:connection_factory_impl.cc(472)] 
ConnectionHandler failed with net error: -2
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.6618] device 
(enp1s0): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.6721] manager: 
NetworkManager state is now ASLEEP
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.6724] device 
(wlp3s0): state change: activated -> deactivating (reason 'sleeping', 
sys-iface-state: 'managed')
Mar  5 20:33:27 rzbox dbus-daemon[998]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.17' (uid=0 
pid=1078 comm="/usr/sbin/NetworkMan
ager --no-daemon" label="unconfined")
Mar  5 20:33:27 rzbox systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Mar  5 20:33:27 rzbox dbus-daemon[998]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Mar  5 20:33:27 rzbox systemd[1]: Started Network Manager Script Dispatcher 
Service.
Mar  5 20:33:27 rzbox kernel: [ 2079.933073] wlp3s0: deauthenticating from 
d4:6e:0e:d9:d5:e7 by local choice (Reason: 3=DEAUTH_LEAVING)
Mar  5 20:33:27 rzbox google-chrome.desktop[4369]: 
[4363:4392:0305/203327.718074:ERROR:connection_factory_impl.cc(427)] Failed to 
connect to MCS endpoint with error -105
Mar  5 20:33:27 rzbox gsd-media-keys[3663]: Unable to get default sink
Mar  5 20:33:27 rzbox update-notifier[5690]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
Mar  5 20:33:27 rzbox wpa_supplicant[1079]: wlp3s0: CTRL-EVENT-DISCONNECTED 
bssid=d4:6e:0e:d9:d5:e7 reason=3 locally_generated=1
Mar  5 20:33:27 rzbox wpa_supplicant[1079]: wlp3s0: CTRL-EVENT-DSCP-POLICY 
clear_all
Mar  5 20:33:27 rzbox wpa_supplicant[1079]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9266] device 
(wlp3s0): supplicant interface state: completed -> disconnected
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9269] device 
(wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', 
sys-iface-state: 'managed')
Mar  5 20:33:27 rzbox avahi-daemon[994]: Withdrawing address record for 
fe80::5525:e62a:821e:1665 on wlp3s0.
Mar  5 20:33:27 rzbox avahi-daemon[994]: Leaving mDNS multicast group on 
interface wlp3s0.IPv6 with address fe80::5525:e62a:821e:1665.
Mar  5 20:33:27 rzbox avahi-daemon[994]: Interface wlp3s0.IPv6 no longer 
relevant for mDNS.
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9683] dhcp4 
(wlp3s0): canceled DHCP transaction
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9683] dhcp4 
(wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9684] dhcp4 
(wlp3s0): state changed no lease
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9687] dhcp6 
(wlp3s0): canceled DHCP transaction
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9687] dhcp6 
(wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Mar  5 20:33:27 rzbox NetworkManager[1078]:   [1678044807.9687] dhcp6 
(wlp3s0): state changed no lease
Mar  5 20:33:27 rzbox avahi-daemon[994]: Withdrawing address record for 
172.16.10.104 on wlp3s0.
Mar  5 20:33:27 rzbox avahi-daemon[994]: Leaving mDNS multicast group on 
interface wlp3s0.IPv4 with address 172.16.10.104.
Mar  5 20:33:27 rzbox systemd-resolved[789]: wlp3s0: Bus client set default 
route setting: no
Mar  5 20:33:27 rzbox systemd-resolved[789]: wlp3s0: Bus client reset DNS 
server list.
Mar  5 20:33:27 rzbox avahi-daemon[994]: Interface wlp3s0.IPv4 no longer 
relevant for mDNS.
Mar 

[Kernel-packages] [Bug 1905132] Re: no audio output dummy only

2020-11-21 Thread Jaromir Obr
I've just found out that upgrade to the latest "groovy-proposed" fixed my issue 
(see the description in 
https://launchpad.net/ubuntu/+source/alsa-lib/1.2.3.2-1ubuntu3.1).
It seems that my issue reported in #1901901 is duplicate of #1901922 .

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

Title:
  no audio output dummy only

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04.
  device: IdeaPad-5-14ARE05
  Since shortly it stopped working and only showed: "System => Sound => Output 
Device" - "Dummy Output".
  Checked it with different kernels and it is not kernel related
  problem since upgrade of libasound, so we set back to older version

  cat /prod/asound/cards

   0 [Generic]: HDA-Intel - HD-Audio Generic
    HD-Audio Generic at 0xd04c8000 irq 90
   1 [Generic_1  ]: HDA-Intel - HD-Audio Generic
    HD-Audio Generic at 0xd04c irq 91
   2 [acp]: acp - acp
    LENOVO-81YM-IdeaPad514ARE05-LNVNB161216

  we figured it to be no pulse problem but with alsa

  solution:

  sudo apt install libasound2=1.2.2-2.1 libasound2-data=1.2.2-2.1
  libasound2:i386=1.2.2-2.1 libatopology2=1.2.2-2.1

  to prevent from upgrades again:

  echo  libasound2 hold | sudo dpkg --set-selections

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

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


[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740

2020-08-26 Thread Jaromir Obr
I had similar issue with Lenovo Yoga Slim 7 AMD Ryzen 4700U, in Ubuntu 20.04.1.
Solved by upgrade of kernel to latest upstream (5.8). Another solution for me 
was installation of AMDGPU proprietary drivers.

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

Title:
  Brightness hotkeys not working on Lenovo S740

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase)
  do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness
  hotkeys did not work on 19.10 either.

  I followed the guide here:
  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  In "Step-by-step Troubleshooting", none of the steps (1-7) did produce
  any reaction to brightness change key combinations. However, I am able
  to change the laptop screen brightness through the brightness applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elias  1447 F pulseaudio
   /dev/snd/controlC0:  elias  1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:12:01 2020
  InstallationDate: Installed on 2019-11-19 (144 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 81RS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago)
  dmi.bios.date: 03/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BYCN33WW
  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 Yoga S740-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL:
  dmi.product.family: Yoga S740-14IIL
  dmi.product.name: 81RS
  dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL
  dmi.product.version: Lenovo Yoga S740-14IIL
  dmi.sys.vendor: LENOVO

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

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