[Bug 1970089] Re: keyboard not working in laptop
REMARK: There seems to be a conflict with elan module. As a successul workaround I disabled the elants_i2c module in grub: GRUB_CMDLINE_LINUX_DEFAULT="initcall_blaclist=elants_i2c" This is just a workaround. However, the internal keyboard seems to work proper in the moment. No negative impact on loading of touchpad module (sudo modprobe i2c-hid-acpi) which is always necessary to get the touchpad working. ** Summary changed: - keyboard not working in laptop + keyboard not working in laptop Fujitsu E5511 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970089 Title: keyboard not working in laptop Fujitsu E5511 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970256] Re: Touchpad not working on laptop Fujitsu E5511
** Summary changed: - Touchpad ELAN not working on laptop Fujitsu E5511 + Touchpad not working on laptop Fujitsu E5511 ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 - Touchpad ELAN not working on laptop Fujitsu E5511 + Touchpad ELAN or DesignWare (??) not working on laptop Fujitsu E5511 The built in touchpad does not work after start of Ubuntu. current installation is new, first start, no updates yet, build in keyboard is working properly. Workaround: start terminal, manually invoke sudo modprobe i2c-hid-acpi makes touchpad work. Expected behaviour: Touchpad works without manual intervention. Question: Could you please investigate if a proper solution is possible or what to do? Remark: login screen still works proper; this is NOT the case any more after very first reboot. - After very first reboot KEYBOARD and TOUCHPAD do not work any longer; login is not possible, no "mouse", no input by built in keyboard; + After very first reboot KEYBOARD and TOUCHPAD do not work any longer; login is not possible, no "mouse", no input by built in keyboard; Remark (after first reboot): Comparing the list of modules before/after invoking "sudo modprobe i2c-hid-acpi" I see this diff: user@machine:~$ diff cat-proc-modules__withKeyBoard.txt cat-proc-modules__noKeyBoard.txt 1,6d0 < joydev 28672 0 - Live 0xc0be < hid_multitouch 28672 0 - Live 0xc09af000 < hid_generic 16384 0 - Live 0xc0962000 < i2c_hid_acpi 16384 0 - Live 0xc06a9000 < i2c_hid 28672 1 i2c_hid_acpi, Live 0xc06bb000 < hid 139264 3 hid_multitouch,hid_generic,i2c_hid, Live 0xc098c000 160c154 < pinctrl_tigerlake 32768 1 - Live 0xc0022000 --- > pinctrl_tigerlake 32768 0 - Live 0xc0022000 I can not understand or interpret this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 19:32:20 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 Touchpad ELAN or DesignWare (??) not working on laptop Fujitsu E5511 The built in touchpad does not work after start of Ubuntu. current installation is new, first start, no updates yet, build in keyboard is working properly. Workaround: start terminal, manually invoke sudo modprobe i2c-hid-acpi makes touchpad work. Expected behaviour: Touchpad works without manual intervention. Question: Could you please investigate if a proper solution is possible or what to do? Remark: login screen still works proper; this is NOT the case any more after very first reboot. After very first reboot KEYBOARD and TOUCHPAD do not work any longer; login is not possible, no "mouse", no input by built in keyboard; Remark (after first reboot): Comparing the list of modules before/after invoking "sudo modprobe i2c-hid-acpi" I see this diff: user@machine:~$ diff cat-proc-modules__withKeyBoard.txt cat-proc-modules__noKeyBoard.txt 1,6d0 < joydev 28672 0 - Live 0xc0be < hid_multitouch 28672 0 - Live 0xc09af000 < hid_generic 16384 0 - Live 0xc0962000 < i2c_hid_acpi 16384 0 - Live 0xc06a9000 < i2c_hid 28672 1 i2c_hid_acpi, Live 0xc06bb000 < hid 139264 3 hid_multitouch,hid_generic,i2c_hid, Live 0xc098c000 160c154 < pinctrl_tigerlake 32768 1 - Live 0xc0022000 --- > pinctrl_tigerlake 32768 0 - Live 0xc0022000 I can not understand or interpret this. + REMARK: + after invoking "sudo modprobe i2c-hid-acpi" dmesg says: + + [ 187.322961] hid: raw HID events driver (C) Jiri Kosina + [ 187.444671] input: 0X45 0X4C 0X41 0X4E 04F3:308C Mouse as /devices/pci:00/:00:15.3/i2c_designware.2/i2c-3/i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308C.0001/input/input30 + [ 187.444829] input: 0X45 0X4C 0X41 0X4E 04F3:308C Touchpad as /devices/pci:00/:00:15.3/i2c_designware.2/i2c-3/i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00/0018:04F3:308C.0001/input/input32 + [ 187.444923] hid-generic 0018:04F3:308C.0001: input,hidraw0: I2C HID v1.00 Mouse [0X45 0X4C 0X41 0X4E 04F3:308C] on i2c-0X45 0X4C 0X41 0X4E 0X30 0X44 0X30 0X30 0X00:00 + [ 187.574129] input: 0X45 0X4C 0X41 0X4E 04F3:308C Mouse as
[Bug 1970256] Re: Touchpad ELAN not working on laptop Fujitsu E5511
** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 Touchpad ELAN not working on laptop Fujitsu E5511 - The built in touchpad does not work after start of Ubuntu. - current installation is new, first start, no updates yet, build in keyboard is working properly. + The built in touchpad does not work after start of Ubuntu. + current installation is new, first start, no updates yet, build in keyboard is working properly. Workaround: start terminal, manually invoke sudo modprobe i2c-hid-acpi - makes touchpad work. + makes touchpad work. Expected behaviour: - Touchpad works without manual intervention. + Touchpad works without manual intervention. - Remark: login screen still works proper + Remark: login screen still works proper; this is NOT the case any more + after very first reboot. + + Remark: + Comparing the list of modules before/after invoking "sudo modprobe i2c-hid-acpi" I see this diff: + + user@machine:~$ diff cat-proc-modules__withKeyBoard.txt cat-proc-modules__noKeyBoard.txt + 1,6d0 + < joydev 28672 0 - Live 0xc0be + < hid_multitouch 28672 0 - Live 0xc09af000 + < hid_generic 16384 0 - Live 0xc0962000 + < i2c_hid_acpi 16384 0 - Live 0xc06a9000 + < i2c_hid 28672 1 i2c_hid_acpi, Live 0xc06bb000 + < hid 139264 3 hid_multitouch,hid_generic,i2c_hid, Live 0xc098c000 + 160c154 + < pinctrl_tigerlake 32768 1 - Live 0xc0022000 + --- + > pinctrl_tigerlake 32768 0 - Live 0xc0022000 + + I can not understand or interpret this. + + + + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 19:32:20 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 Touchpad ELAN not working on laptop Fujitsu E5511 The built in touchpad does not work after start of Ubuntu. current installation is new, first start, no updates yet, build in keyboard is working properly. Workaround: start terminal, manually invoke sudo modprobe i2c-hid-acpi makes touchpad work. Expected behaviour: Touchpad works without manual intervention. - Remark: login screen still works proper; this is NOT the case any more - after very first reboot. + Question: + Could you please investigate if a proper solution is possible or what to do? - Remark: + Remark: login screen still works proper; this is NOT the case any more after very first reboot. + After very first reboot KEYBOARD and TOUCHPAD do not work any longer; login is not possible, no "mouse", no input by built in keyboard; + + Remark (after first reboot): Comparing the list of modules before/after invoking "sudo modprobe i2c-hid-acpi" I see this diff: - user@machine:~$ diff cat-proc-modules__withKeyBoard.txt cat-proc-modules__noKeyBoard.txt + user@machine:~$ diff cat-proc-modules__withKeyBoard.txt cat-proc-modules__noKeyBoard.txt 1,6d0 < joydev 28672 0 - Live 0xc0be < hid_multitouch 28672 0 - Live 0xc09af000 < hid_generic 16384 0 - Live 0xc0962000 < i2c_hid_acpi 16384 0 - Live 0xc06a9000 < i2c_hid 28672 1 i2c_hid_acpi, Live 0xc06bb000 < hid 139264 3 hid_multitouch,hid_generic,i2c_hid, Live 0xc098c000 160c154 < pinctrl_tigerlake 32768 1 - Live 0xc0022000 --- > pinctrl_tigerlake 32768 0 - Live 0xc0022000 I can not understand or interpret this. - - - - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 19:32:20 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you
[Bug 1970256] [NEW] Touchpad ELAN not working on laptop Fujitsu E5511
Public bug reported: Description:Ubuntu 20.04.4 LTS Release:20.04 Touchpad ELAN not working on laptop Fujitsu E5511 The built in touchpad does not work after start of Ubuntu. current installation is new, first start, no updates yet, build in keyboard is working properly. Workaround: start terminal, manually invoke sudo modprobe i2c-hid-acpi makes touchpad work. Expected behaviour: Touchpad works without manual intervention. Remark: login screen still works proper ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 19:32:20 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970256 Title: Touchpad ELAN not working on laptop Fujitsu E5511 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1970256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970093] [NEW] interface status communication fails: state UNKNOWN persists for GSM-modem Sierra Wireless EM7421
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy 5.15.0-27-generic Bus 003 Device 002: ID 1199:90b1 Sierra Wireless, Inc. EM7421 network-manager: Installed: 1.36.4-2ubuntu1 modem manager can not report proper interface status for GSM Modem; ALWAYS "state UNKNOWN" even if successful connection. Expected: State reported as UP or DOWN etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Apr 24 12:58:51 2022 InstallationDate: Installed on 2022-03-06 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) IpRoute: default via 10.34.43.5 dev wwan0 proto static metric 700 10.34.43.0/29 dev wwan0 proto kernel scope link src 10.34.43.4 metric 700 169.254.0.0/16 dev wwan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Description changed: Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy 5.15.0-27-generic Bus 003 Device 002: ID 1199:90b1 Sierra Wireless, Inc. EM7421 network-manager: Installed: 1.36.4-2ubuntu1 - - modem manager can not report proper interface status for GSM Modem; - ALWAYS "state UNKNOWN" even if successfully connecting. + modem manager can not report proper interface status for GSM Modem; + ALWAYS "state UNKNOWN" even if successful connection. Expected: State reported as UP or DOWN etc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Apr 24 12:58:51 2022 InstallationDate: Installed on 2022-03-06 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) IpRoute: - default via 10.34.43.5 dev wwan0 proto static metric 700 - 10.34.43.0/29 dev wwan0 proto kernel scope link src 10.34.43.4 metric 700 - 169.254.0.0/16 dev wwan0 scope link metric 1000 + default via 10.34.43.5 dev wwan0 proto static metric 700 + 10.34.43.0/29 dev wwan0 proto kernel scope link src 10.34.43.4 metric 700 + 169.254.0.0/16 dev wwan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.36.4 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.36.4 connected started full enabled enabled enabled enabled enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970093 Title: interface status communication fails: state UNKNOWN persists for GSM- modem Sierra Wireless EM7421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1970093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970086] Re: GSM modem does not work properly (driver / config issue)
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970086 Title: GSM modem does not work properly (driver / config issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1970086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970086] Re: GSM modem does not work properly (driver / config issue)
remark: The issue with the broken GSM-modem-driver did NOT appear during fresh installation (online update during installation was NOT enabled). The problem kicked in immediately after very first online update (in last state of installation and before very first reboot). ** Also affects: libmbim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970086 Title: GSM modem does not work properly (driver / config issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1970086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970089] [NEW] keyboard not working in laptop
Public bug reported: Description:Ubuntu 21.10 Release:21.10 Keyboard not working on Laptop after booting successful. Expected: built in keyboard can be used to invoke password keyboard not working in laptop after booting Ubuntu 21.10 Login not possible, password can not be inserted in GUI (lightdm but can be other like gdm3 or gddm or slim, no impact) because keyboard is not responding at all (not even special keys). The keyboard is working before boot so grub etc can be controlled. Hence it is disabled by Ubuntu. External USB-keyboard is working. Does not make internal keyboard work. Special: When the lid is closed and Ubuntu suspends properly and then the lid is opened and Ubuntu resumes properly then the keyboard is working! This defect is found in all Ubuntu 18, 19, 20, 21 and XUbuntu 18 to 21.10. Issue does not appear in Ubuntu 22.04 / XUbuntu 22.04. U 22.04 upgrade is no option due to failing GSM-modem control in all 22.04 versions. It did NOT HELP to disable intel vbtn -tablet mode by blacklisting intel_vbtn. Presumably the issue is related to the ill fated "tablet mode" The machine is Fujitsu E5511. Can you please point out a workaround to enableth keyboard? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-40-generic 5.13.0-40.45 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sysyadmin 1239 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Apr 24 11:35:59 2022 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5511 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=deadea51-80db-4ccb-8008-10cbbc002aba ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-40-generic N/A linux-backports-modules-5.13.0-40-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 2.28 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.28 dmi.board.name: FJNB2E8 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: C3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5511 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.28:bd03/17/2022:br2.28:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5511:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E8:rvrC3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5511:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5511 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970089 Title: keyboard not working in laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970086] [NEW] GSM modem does not work properly (driver / config issue)
Public bug reported: The GSM Modem does not work properly in Network. There is no IPv6 connection. Modem is Sierra Wireless, Inc. EM7421 GSM Modem EM7421 works perfect with Xubuntu 21.10 and it works perfect with Ubuntu 21.10. SIM card, APN etc. same as in U21.10 do work fine (same machine Fujitsu E5511). Need to correct broken settings to get EM7421 properly show and handle IPv6 connections. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sysyadmin 1066 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Apr 24 10:50:46 2022 InstallationDate: Installed on 2022-04-24 (0 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5511 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=adf3ffda-d8d8-4b33-9786-041e074965c7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 2.28 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.28 dmi.board.name: FJNB2E8 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: C3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5511 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.28:bd03/17/2022:br2.28:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5511:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E8:rvrC3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5511:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5511 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970086 Title: GSM modem does not work properly (driver / config issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802113] Re: simple-image-reducer crashes in U 18.04
the issue did not appear in recent releases of Ubuntu. I did not experience it for more than a year. I consider this bug to be fixed. Question: What can I do to get the bug closed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802113 Title: simple-image-reducer crashes in U 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-image-reducer/+bug/1802113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
apport information ** Tags added: apport-collected jammy third-party-packages ** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: - SIM is working properly, - EM7421 latest firmware applied, - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10 + works with Linux Mint); "package" not understood, sorry. ModemManager probably? ASSUMPTIONs: - Missing IPv6 is a wrong config / bug in software / communication issue. - IPv6 communication can be enabled by adjustment rather than by code changes in cdc_mbim or redesign of SierraW. EM7421 device. - Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well. It shows other issues like missing provision of additional DNS server data, EUI64 state and the like. THE ISSUE and details: Actually no IPv6 available at all (IPv6 is expected to work / no IPv6 is a big issue for our work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration:
[Bug 1969241] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1969241/+attachment/5581065/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969241 Title: Network issue no IPv6 using Sierra Wireless EM7421 and mbim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1969241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: - SIM is working properly, - EM7421 latest firmware applied, - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); - "package" unknown, sorry. ModemManager probably? + - SIM is working properly, + - EM7421 latest firmware applied, + - EM7421 capable doing IPv6 with this setup (according to spec + test with Win10 + works with Linux Mint); - ASSUMPTION: - Missing IPv6 is a wrong config / bug in software. - IPv6 communication can be enabled. - Some enhancement / fix can enable IPv6 communication. + "package" not understood, sorry. ModemManager probably? + + ASSUMPTIONs: + - Missing IPv6 is a wrong config / bug in software / communication issue. + - IPv6 communication can be enabled. + - Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). - It uses driver=cdc_mbim as well + It uses driver=cdc_mbim as well. It shows other issues like missing provision of additional DNS server data, EUI64 state and the like. details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0
[Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: - IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. - IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. + IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. + IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. All using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); "package" unknown, sorry. ModemManager probably? ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. REMARK: Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product: xHCI Host Controller vendor: Linux 5.15.0-25-generic xhci-hcd
[Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: - IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. Using the same driver=cdc_mbim + IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. + IPv6 shall work properly like in Linux-Mint 20.3 on this machine, this setup. + All using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); - "package" unknown, sorry. + "package" unknown, sorry. ModemManager probably? ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. - REMARK: - Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). + REMARK: + Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). It uses driver=cdc_mbim as well details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0
[Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. Using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); "package" unknown, sorry. ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. + + REMARK: + Linux-Mint 20.3 una is capable of running the 'EM7421' in proper IPv6 "mode" (kernel 5.4.0-107-generic). + It uses driver=cdc_mbim as well details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product: xHCI Host Controller vendor: Linux 5.15.0-25-generic xhci-hcd physical id: 0 bus info: usb@3 logical name: usb3 version: 5.15 capabilities: usb-2.00 configuration: driver=hub slots=12 speed=480Mbit/s *-usb:0
[Bug 1969241] Re: Network issue no IPv6 using Sierra Wireless EM7421 and mbim
** Description changed: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. Using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); "package" unknown, sorry. ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product: xHCI Host Controller vendor: Linux 5.15.0-25-generic xhci-hcd physical id: 0 bus info: usb@3 logical name: usb3 version: 5.15 capabilities: usb-2.00 configuration: driver=hub slots=12 speed=480Mbit/s *-usb:0 description: Communication device product: EM7421 vendor: Sierra Wireless, Incorporated physical id:
[Bug 1969241] [NEW] Network issue no IPv6 using Sierra Wireless EM7421 and mbim
Public bug reported: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Description:Ubuntu Jammy Jellyfish Release:22.04 Linux 5.15.0-25-generic I need to connect via GSM to Internet using IPv6. IPv6 not present in config. Internet connect works with IPv4 although issues seem to exist. EXPECTATION: IPv6 shall work properly like the EM7455 with same card in very similar machine, Ubuntu. Using the same driver=cdc_mbim ENVIRONMENT: SIM is working properly, EM7421 latest firmware applied, EM7421 capable doing IPv6 with this setup (according to spec + test with Win10); "package" unknown, sorry. ASSUMPTION: Missing IPv6 is a wrong config / bug in software. IPv6 communication can be enabled. Some enhancement / fix can enable IPv6 communication. details: Actually no IPv6 available at all (IPv6 is expected to work): 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 6a:05:2c:26:95:58 brd ff:ff:ff:ff:ff:ff inet 10.34.85.36/29 brd 10.34.85.39 scope global noprefixroute wwan0 This is the Sierra Wireless GSM-Modem (working): sudo mbimcli --device=/dev/cdc-wdm0 --query-device-caps [/dev/cdc-wdm0] Device capabilities retrieved: Device type: 'remote' Cellular class: 'gsm' Voice class: 'no-voice' SIM class: 'removable' Data class: 'umts, hsdpa, hsupa, lte' SMS caps: 'pdu-receive, pdu-send' Ctrl caps: 'reg-manual' Max sessions: '8' Custom data class: 'unknown' Device ID: '356706140353162' Firmware info: 'SWI9X50C_01.14.03.00' Hardware info: 'EM7421' Attempt to start modem via mbim: pre: sudo service network-manager stop sudo systemctl disable ModemManager then Report sudo mbim-network /dev/cdc-wdm0 start Profile at '/etc/mbim-network.conf' not found... Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close'... [/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '262011905110762' SIM ICCID: '8949021788157884' Ready info: 'none' Telephone numbers: (1) '+491604282867' [/dev/cdc-wdm0] Session not closed: TRID: '3' Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close'... [/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '26201' Provider name: 'Telekom.de' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '4' Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close'... [/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: 'unknown' Packet service state: 'attached' Available data classes: 'lte' Uplink speed: '15000 bps' Downlink speed: '3 bps' [/dev/cdc-wdm0] Session not closed: TRID: '5' Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='' --no-open=5 --no-close'... Network started successfully Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 7) status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff try to bring it up: sudo ip link set dev wwan0 up (no error reported) new status reported by ip a : 3: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 86:a6:1f:1a:ce:30 brd ff:ff:ff:ff:ff:ff (All SIM / telephony / GSM data above is real; please handle with care) lshw reporting on USB and the like *-usb:2 description: USB controller product: Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 20 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:155 memory:5c42-5c42 *-usbhost:0 product: xHCI Host Controller vendor: Linux 5.15.0-25-generic xhci-hcd physical id: 0 bus info: usb@3 logical name: usb3 version: 5.15 capabilities: usb-2.00 configuration: driver=hub slots=12 speed=480Mbit/s *-usb:0 description: Communication device product: EM7421 vendor: Sierra Wireless, Incorporated physical id: 3 bus info: usb@3:3 version: 0.06 serial: 8G1202758803B121 capabilities: usb-2.00 configuration: driver=cdc_mbim maxpower=500mA
[Bug 1956845] [NEW] Xorg crash
Public bug reported: this is additional information related to [Bug 1955049] about amdgpu kernel errors. The test of kernel 5.16.0-051600rc8drmtip20220105-generic is quite promising: This is the first crash after several hours of use. So this report is related to Bug 1955049. This report is created using SSH connection to the machine because the GUI did not "come back" after the crash. A subsequent reboot will be conducted soon after submitting this report. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.16.0-051600rc8drmtip20220105-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 9 00:29:39 2022 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211218: added ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (388 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.16.0-051600rc8drmtip20220105-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Sat Jan 8 22:03:14 2022 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956845 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954956] Re: [amdgpu] System crash
Description:Ubuntu 21.04 Release:21.04 amended kernel info: 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954956 Title: [amdgpu] System crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955049] [NEW] Xorg crash
Public bug reported: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. Description:Ubuntu 21.04 Release:21.04 GUI crashed: Operation ceses, monitor becomes dark. In this case the monitor shows a static picture after some seconds of darkness. Remote access via SSH is possible up to some extend. Expected: GUI does not crash. dmesg says: [ 2284.101478] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 2289.993462] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=132409, emitted seq=132410 [ 2289.993826] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [ 2289.994175] amdgpu :0a:00.0: amdgpu: GPU reset begin! [ 2290.169982] [drm] free PSP TMR buffer [ 2290.198611] amdgpu :0a:00.0: amdgpu: MODE2 reset [ 2290.198656] amdgpu :0a:00.0: amdgpu: GPU reset succeeded, trying to resume [ 2290.198943] [drm] PCIE GART of 1024M enabled. [ 2290.198945] [drm] PTB located at 0x00F40090 [ 2290.199115] [drm] PSP is resuming... [ 2290.218996] [drm] reserve 0x40 from 0xf45700 for PSP TMR [ 2290.262318] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 2290.266897] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 2290.266899] amdgpu :0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 2290.468265] [drm] kiq ring mec 2 pipe 1 q 0 [ 2290.602777] [drm] VCN decode and encode initialized successfully(under SPG Mode). [ 2290.602784] amdgpu :0a:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [ 2290.602787] amdgpu :0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 2290.602788] amdgpu :0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 2290.602790] amdgpu :0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 2290.602791] amdgpu :0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 2290.602792] amdgpu :0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 2290.602795] amdgpu :0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 2290.602796] amdgpu :0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 2290.602797] amdgpu :0a:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [ 2290.602799] amdgpu :0a:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [ 2290.602800] amdgpu :0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [ 2290.609397] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow start [ 2290.609400] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow done [ 2290.609464] amdgpu :0a:00.0: amdgpu: GPU reset(1) succeeded! [ 2290.609926] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 2290.609979] kfd kfd: amdgpu: error getting iommu info. is the iommu enabled? [ 2290.609981] kfd kfd: amdgpu: Error initializing iommuv2 [ 2290.610175] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors [ 2317.591058] rfkill: input handler enabled [ 2412.382743] show_signal_msg: 29 callbacks suppressed [ 2412.382746] apport-gtk[16593]: segfault at 18 ip 7f7f7e90e194 sp 7fff2ca56790 error 4 in libgtk-3.so.0.2404.21[7f7f7e805000+385000] [ 2412.382753] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 8c 3c 17 00 <48> 8b 40 18 48 8b 78 10 e8 df 03 09 00 48 83 c4 08 48 89 c7 e9 a3 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 16 14:34:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (365 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine:
[Bug 1954956] [NEW] Xorg crash
Public bug reported: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Dec 15 15:19:50 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954956 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1954956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
sorry, my stupid fault. Now it says peter:~/Downloads$ uname -a Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux And I'll keep looking at it. Sorry for the confusion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944122] [NEW] Xorg crash
Public bug reported: in the middle of working the GUI crashed (mouse movements yes, no klicks possible) came back, crashed again, login screen appeared. Clearly an issue with AMD-GPU as dmesg states. This report was only possible via ssh from a different machine. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Sep 20 14:26:27 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20210418, 5.11.0-34-generic, x86_64: installed vhba, 20210418, 5.11.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (278 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Mon Sep 20 14:25:30 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.1 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu ** Attachment added: "dmesg_20sep2021crasing_APU.txt" https://bugs.launchpad.net/bugs/1944122/+attachment/5526448/+files/dmesg_20sep2021crasing_APU.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944122 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
in reply to message #31: I'm very sorry for all your hard work: does not install, dependency problems. doing some "sudo dpkg-reconfigure" did not help at all. looks like this: dietmar@peter:~/Downloads$ sudo dpkg -i linux-image-unsigned-5.14.0-051400drmtip20210904-generic_5.14.0-051400drmtip20210904.202109040225_amd64.deb (Lese Datenbank ... 499642 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von linux-image-unsigned-5.14.0-051400drmtip20210904-generic_5.14.0-051400drmtip20210904.202109040225_amd64.deb ... Entpacken von linux-image-unsigned-5.14.0-051400drmtip20210904-generic (5.14.0-051400drmtip20210904.202109040225) über (5.14.0-051400drmtip20210904.202109040225) ... dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-unsigned-5.14.0-051400drmtip20210904-generic: linux-image-unsigned-5.14.0-051400drmtip20210904-generic hängt ab von linux-modules-5.14.0-051400drmtip20210904-generic; aber: Paket linux-modules-5.14.0-051400drmtip20210904-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-image-unsigned-5.14.0-051400drmtip20210904-generic (--install): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: linux-image-unsigned-5.14.0-051400drmtip20210904-generic dietmar@peter:~/Downloads$ dietmar@peter:~/Downloads$ sudo dpkg -i linux-modules-5.14.0-051400drmtip20210904-generic_5.14.0-051400drmtip20210904.202109040225_amd64.deb (Lese Datenbank ... 499642 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von linux-modules-5.14.0-051400drmtip20210904-generic_5.14.0-051400drmtip20210904.202109040225_amd64.deb ... Entpacken von linux-modules-5.14.0-051400drmtip20210904-generic (5.14.0-051400drmtip20210904.202109040225) über (5.14.0-051400drmtip20210904.202109040225) ... dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-modules-5.14.0-051400drmtip20210904-generic: linux-modules-5.14.0-051400drmtip20210904-generic hängt ab von linux-image-5.14.0-051400drmtip20210904-generic | linux-image-unsigned-5.14.0-051400drmtip20210904-generic; aber: Paket linux-image-5.14.0-051400drmtip20210904-generic ist nicht installiert. Paket linux-image-unsigned-5.14.0-051400drmtip20210904-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-modules-5.14.0-051400drmtip20210904-generic (--install): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: linux-modules-5.14.0-051400drmtip20210904-generic dietmar@peter:~/Downloads$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
status prior(!) to message #31 : crashing; see attachment ** Attachment added: "peter_07sep21_crash_kernel5.11.0-34-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+attachment/5523477/+files/peter_07sep21_crash_kernel5.11.0-34-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
"The requested URL was not found on this server." is what I get when I try to download the dep-packages mentioned before. Feedback: The machine wilhelm with kernel 5.11.0-34-generic experiences plenty of crashes, running instable. Completely different applications running when GUI suddenly freezes and most times whole OS is stale. Machine with 5.11.0-34-generic kernel crashes not often. Sometimes just killing all applications then restarting the GUI login screen (on this machine sddm window manager). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
Thanks a lot for your swift reply and many Thanks to the developers!
I can not verify GUI issue reliable and reproducible because the most affected
machine is remote via ssh.
Status:
The most affected machine "Wilhelm" did NOT show the issue since about 2days.
The level is:
Linux wilhelm 5.4.0-83-generic #93-Ubuntu SMP Tue Aug 17 10:15:03 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04.3 LTS ("proposed" enabled, NOT
applied linux-generic-hwe-20.04 since it is a production machine)
I assume the 2-day-no-crash situation on wilhelm may indicate successful
improvements.
Another affected machine will now be observed having kernel level:
Linux peter 5.11.0-33-generic #35-Ubuntu SMP Mon Aug 16 23:50:22 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux 21.04 hirsute ("proposed" enabled)
Here I could apply "generic-hwe" but for 21.04 it seems to be unavailable.
A third strongly affected AMD-APU 20.04.3 LTS machine (remote, ssh) is
not in use currently (insignificance of any result). However it is now
updated to: Linux Devon 5.4.0-83-generic #93-Ubuntu SMP Tue Aug 17
10:15:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
If I can find any current issue I will report it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939417
Title:
Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT,
amdgpu :09:00.0: [gfxhub0] retry page fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940781] Re: Xorg freeze
dmesg immediately taken after crash happened: [ 7974.752159] amdgpu :0a:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:2 pasid:32770, for process gnome-shell pid 3588 thread gnome-shel:cs0 pid 3611) [ 7974.752163] amdgpu :0a:00.0: amdgpu: in page starting at address 0x80014df0f000 from client 27 [ 7974.752168] amdgpu :0a:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 7974.752174] amdgpu :0a:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) [ 7974.752178] amdgpu :0a:00.0: amdgpu: MORE_FAULTS: 0x0 [ 7974.752180] amdgpu :0a:00.0: amdgpu: WALKER_ERROR: 0x0 [ 7974.752183] amdgpu :0a:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 7974.752185] amdgpu :0a:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 7974.752188] amdgpu :0a:00.0: amdgpu: RW: 0x0 [ 7974.752197] amdgpu :0a:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:2 pasid:32770, for process gnome-shell pid 3588 thread gnome-shel:cs0 pid 3611) [ 7974.752203] amdgpu :0a:00.0: amdgpu: in page starting at address 0x80014df1 from client 27 [ 7974.752209] amdgpu :0a:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x [ 7974.752220] amdgpu :0a:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) [ 7974.752223] amdgpu :0a:00.0: amdgpu: MORE_FAULTS: 0x0 [ 7974.752225] amdgpu :0a:00.0: amdgpu: WALKER_ERROR: 0x0 [ 7974.752228] amdgpu :0a:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 7974.752230] amdgpu :0a:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 7974.752232] amdgpu :0a:00.0: amdgpu: RW: 0x0 ** Attachment added: "dmesg_Peter-crash_22aug21.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1940781/+attachment/5519892/+files/dmesg_Peter-crash_22aug21.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940781 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1940781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940781] [NEW] Xorg freeze
Public bug reported: machine was running stable for hours then crashed the GUI - submission of bug report via ssh from different host. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-33.35-generic 5.11.22 Uname: Linux 5.11.0-33-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Aug 22 22:21:03 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20210418, 5.11.0-31-generic, x86_64: installed vhba, 20210418, 5.11.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (249 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-33-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Sun Aug 22 20:29:10 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.1 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940781 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1940781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940690] Re: Xorg crash
this is a duplicate of #1939417. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940690 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1940690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519541/+files/modified.conffile..etc.apport.crashdb.conf.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519540/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519539/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519538/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519536/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519537/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519535/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519534/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519533/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519532/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519531/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519530/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519529/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519527/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519528/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519526/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1939417/+attachment/5519525/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
apport information ** Tags added: apport-collected ** Description changed: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d3ff] usable [0.00] BIOS-e820: [mem
[Bug 1940690] [NEW] Xorg crash
Public bug reported: [0.00] Linux version 5.4.0-81-generic (buildd@lgw01-amd64-052) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 (Ubuntu 5.4.0-81.91-generic 5.4.128) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-81-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [ 217.837643] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.837647] amdgpu :09:00.0: in page starting at address 0x80010797e000 from client 27 [ 217.837649] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.837651] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.837653] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.837655] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.837657] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.837658] amdgpu :09:00.0: RW: 0x0 [ 217.837668] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.837670] amdgpu :09:00.0: in page starting at address 0x8001079a6000 from client 27 [ 217.837672] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.837674] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.837675] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.837677] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.837679] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.837681] amdgpu :09:00.0: RW: 0x0 [ 217.837698] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.837703] amdgpu :09:00.0: in page starting at address 0x8001079ce000 from client 27 [ 217.837708] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.837712] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.837716] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.837721] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.837725] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.837729] amdgpu :09:00.0: RW: 0x0 [ 217.838669] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.838673] amdgpu :09:00.0: in page starting at address 0x80010797e000 from client 27 [ 217.838675] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.838677] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.838679] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.838681] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.838683] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.838684] amdgpu :09:00.0: RW: 0x0 [ 217.838695] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.838697] amdgpu :09:00.0: in page starting at address 0x8001079a6000 from client 27 [ 217.838699] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.838701] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.838703] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.838704] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.838706] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.838708] amdgpu :09:00.0: RW: 0x0 [ 217.838727] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.838732] amdgpu :09:00.0: in page starting at address 0x8001079ce000 from client 27 [ 217.838736] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.838741] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.838746] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.838750] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.838755] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.838759] amdgpu :09:00.0: RW: 0x0 [ 217.839694] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7499 thread Xorg:cs0 pid 7500) [ 217.839698] amdgpu :09:00.0: in page starting at address 0x80010797e000 from client 27 [ 217.839700] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 217.839702] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 217.839703] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 217.839705] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 217.839707] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 217.839709] amdgpu :09:00.0: RW: 0x0 [ 217.992553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
attached please find a new log - set about the most recent crash. Trailing there is the result of "uname -a" in the log file. ** Attachment added: "dmesg_20aug2021_wilhelm_AMD-APU__VM_L2_PROTECTION_FAULT_STATUS.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+attachment/5519400/+files/dmesg_20aug2021_wilhelm_AMD-APU__VM_L2_PROTECTION_FAULT_STATUS.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
a preliminary test with a kernel 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux did not show the crash yet. I do not consider this to be a reliable test but at least it indicates a significantly more stable behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
Thanks for the reply. Currently I only have limited, remote access. I can not test properly in the moment. I try to conduct testing the GUI asap but that can take weeks. Thanks for your help I try to catch up as soon as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
probably affected package: xorg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
** Description changed: Ubuntu GUI crashes (w and w/o Wayland) - on a Ryzen APU machine - sometimes total OS crash, sometimes ssh access still possible. + on + AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) + + sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using - the GUI crashes at different times in different situations, no specific application or package identified. + the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen - Ubuntu working, applications like LibreOffice do their job. + Ubuntu working, applications like LibreOffice do their job. 4) What happened instead - OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. - - Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; - no issues experienced when accessing machine via ssh (remote). - - - dmesg says: + No input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. + Sometimes remote ssh reboot possible. + + Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; + no issues experienced when accessing machine via ssh (remote). + + dmesg says: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls - [0.00] zhaoxin Shanghai + [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu:
[Bug 1939417] [NEW] Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
Public bug reported: Ubuntu GUI crashes (w and w/o Wayland) on a Ryzen APU machine sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). dmesg says: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d3ff] usable [0.00] BIOS-e820: [mem 0x0009d400-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x09d01fff] usable [0.00] BIOS-e820: [mem 0x09d02000-0x09ff] reserved [0.00] BIOS-e820: [mem 0x0a00-0x0a1f] usable [0.00] BIOS-e820: [mem 0x0a20-0x0a20afff] ACPI NVS [0.00] BIOS-e820: [mem 0x0a20b000-0x0aff] usable [0.00] BIOS-e820: [mem 0x0b00-0x0b01] reserved [0.00] BIOS-e820: [mem
[Bug 1927152] [NEW] upgrade has aborted due to error in mosquitto while upgrading Ubuntu 20.10 to 21.04
Public bug reported: Error in mosquitto while upgrading Ubuntu 20.10 to 21.04: Errors were encountered while processing: mosquitto Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Setting up mosquitto (2.0.10-3) ... chown: cannot access '/run/mosquitto': No such file or directory dpkg: error processing package mosquitto (--configure): installed mosquitto package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: mosquitto Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] - - - - - The software mosquitto (MQTT) was installed and successfully working in the old Ubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.8.0-52.59-generic 5.8.18 Uname: Linux 5.8.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Tue May 4 21:24:19 2021 InstallationDate: Installed on 2020-04-06 (393 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to hirsute on 2021-05-04 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.apport.crashdb.conf: 2021-05-04T21:23:56.443838 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927152 Title: upgrade has aborted due to error in mosquitto while upgrading Ubuntu 20.10 to 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879953] [NEW] installer crashes U20.04
Public bug reported: reproducible the installer crashes after partitioning and name-setting but before manual configuration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:30:53 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879953 Title: installer crashes U20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1879953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend
I experience the same. With XFCE4-Ubuntu 18.04, 18.10, 20.04 (all, no difference). I removed light-locker completely - no difference. In situations where time triggers locking the unlock screen sometimes appears. Closing the lid there is the problem described in the bug report above. Workaround: After opening the lid I type my password into the void and sesame opens the door! Recap: xfce4-screensaver actually uses the lock screen when closing the lid but does not show it. 100% reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731769] Re: No LUKS password prompt - plymouth
partly solved: In Ubuntu 19.x the GUI-Plymouth does request the password - fine! In non-silent (CLI) mode the password is requested now. Issue: Other text makes it difficult to see the password requesting line. You need to be decently familiar to the situation to identify the password request. This can not be assumed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731769 Title: No LUKS password prompt - plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1731769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823474] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: frequently fails; Devon:~$ systemctl status ssh * ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Sa 2019-04-06 17:42:35 CEST; 5min ago Process: 15706 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Apr 6 11:17:53 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-12-08 (119 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823474 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1823474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802113] [NEW] simple-image-reducer crashes in U 18.04
Public bug reported: simple-image-reducer crashes w/o a error message in U 18.04 and in U18.10 If simple-image-reducer starts from GUI or from CLI it is possible to add file addresses/names to proceed. The setiings / options can be chosen. When the "Execute" button is pressed the simple-image-reducer window disappears. There are no result files written. Starting fom CLI (just type simple-image-reducer at prompt and enter) does not even return an error. I was not able to identify any related entries in /var/log/syslog or in dmesg. This bug is present on 4 of our machines. All are running U18.n and have been updated from U 16.n. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: simple-image-reducer 1.0.2-7 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 7 15:32:15 2018 InstallationDate: Installed on 2016-09-02 (795 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all SourcePackage: simple-image-reducer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: simple-image-reducer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802113 Title: simple-image-reducer crashes in U 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-image-reducer/+bug/1802113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801805] [NEW] pdf printer provided by cups-pdf has disappeared since update to 18.04
Public bug reported: Since the update from Ubuntu 16.n to Ubuntu 18.04 the PDF printer functionality provided by cups-pdf has disappeared (on several machines). The "printer" just disappeared from the list of available printers. In all cases the functionality worked properly before. It is possible to install or re-install the cups-pdf via "apt-get install" and it does run the install. However, the "printer" remains unavailable, no trace. There is no error message visible of whatever kind. Printing from applications using Cups-PDF-printer is no longer possible because there is no Cups-PDF printer no more. Same bug applies to 18.10, too. Please advise how to get back the PDF printer functionality in 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 23:12:26 2018 InstallationDate: Installed on 2016-09-02 (793 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) KernLog: [ 871.633929] audit: type=1400 audit(1541455672.543:64): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/local/lib/libgcrypt.so.20.1.3" pid=6089 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1002 ouid=0 [ 871.634375] audit: type=1400 audit(1541455672.543:65): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/local/lib/libgpg-error.so.0.20.0" pid=6089 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1002 ouid=0 Lpstat: device for DESKJET-990C-2: hp:/usb/DeskJet_990C?serial=ES0B81C11DLG device for Hewlett-Packard-HP-LaserJet-MFP-M725: hp:/net/HP_LaserJet_MFP_M725?zc=NPI02EAAF device for HP-LaserJet-5: socket://192.168.22.65:9100 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b563 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK A556/G Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DESKJET-990C-2.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-MFP-M725.ppd', '/etc/cups/ppd/HP-LaserJet-5.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DESKJET-990C-2.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-MFP-M725.ppd: Permission denied grep: /etc/cups/ppd/HP-LaserJet-5.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic root=UUID=1f7b9a32-c877-4663-b036-c761cde32cfd ro plymouth:debug drm.debug=0xe SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB47 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK A556/G dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.18:bd09/22/2016:svnFUJITSU:pnLIFEBOOKA556/G:pvr:rvnFUJITSU:rnFJNBB47:rvr:cvnFUJITSU:ct10:cvrLIFEBOOKA556/G: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A556/G dmi.sys.vendor: FUJITSU ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801805 Title: pdf printer provided by cups-pdf has disappeared since update to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731769] Re: No LUKS password prompt - plymouth
The same issue applies for Ubuntu 18.10. Other bugs have a similar focus: Ubuntu [Bug 1359689] cryptsetup password prompt not shown Debian Bug report logs - #752752 plymouth: cryptsetup password prompt not shown anymore Fedora Bug 902400 - Plymouth doesn't prompt for LUKS passphrase This is evidence there is actually an issue in plymouth. It is an obstacle for average users to use encryption. Moreover feedback from a wrong password entry is not accurately visible - this is another handling issue. This is more than a bagatelle. Please try to analyse and fix. ** Tags removed: luks ** Tags added: plymouth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731769 Title: No LUKS password prompt - plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1731769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731769] Re: No LUKS password prompt - plymouth
** Summary changed: - No luks password prompt - plymouth + No LUKS password prompt - plymouth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731769 Title: No LUKS password prompt - plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1731769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731769] Re: No luks password prompt - plymouth
Since a few weeks I can see the line with the password request in Ubuntu 18.04 . Can not verify for Fedora. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731769 Title: No luks password prompt - plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1731769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731769] Re: No luks password prompt - plymouth
This bug affects many more users. It is present in Ubuntu 18 as well as in Fedora 27 (experience / both are on my machines). This bug reduces the acceptance by "normal" users even more. I do consider fixing this stupid display error would be an important contribution to propel encryption with normal users. Moreover: It is a bug and it devastates a great tool! ** Also affects: cryptsetup (Fedora) Importance: Undecided Status: New ** Tags added: luks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731769 Title: No luks password prompt - plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1731769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436168] Re: systemd-journald crashed with SIGABRT in journal_file_move_to_object()
I get the bug in 18.04 - what does this mean? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436168 Title: systemd-journald crashed with SIGABRT in journal_file_move_to_object() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1436168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760379] [NEW] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [colord-sane:11175]
Public bug reported: machine successfully kept ssh connect open to a 2nd machine over night. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2951 F pulseaudio dietmar5359 F pulseaudio /dev/snd/controlC0: gdm2951 F pulseaudio dietmar5359 F pulseaudio Date: Sun Apr 1 00:48:23 2018 Failure: oops HibernationDevice: RESUME=UUID=6cc53691-8a2d-45f2-a78c-e5126db414aa MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro plymouth:debug drm.debug=0xe PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [colord-sane:11175] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-oops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760379 Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [colord-sane:11175] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759401] [NEW] package cinnamon-common 3.6.7-3 failed to install/upgrade: installed cinnamon-common package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1759127 *** https://bugs.launchpad.net/bugs/1759127 Public bug reported: after regular update (by GUI) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cinnamon-common 3.6.7-3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 23:26:25 2018 ErrorMessage: installed cinnamon-common package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: cinnamon Title: package cinnamon-common 3.6.7-3 failed to install/upgrade: installed cinnamon-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cinnamon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759401 Title: package cinnamon-common 3.6.7-3 failed to install/upgrade: installed cinnamon-common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1759401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756616] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: upgrade to 18.04 under XFCE ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 17 23:46:15 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-09-02 (560 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756616 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1756616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731769] [NEW] No luks password prompt - plymouth
Public bug reported: No luks password prompt - plymouth NON root LUKS block device encryption (no initram involved) Bug 1359689 Ubuntu or Red Hat(!) Bugzilla – Bug 1086972 are still valid. With Ubuntu 17.10 in November 2017 the problem remains: It is a Plymouth issue, not an issue of LUKS or NVIDIA or Linux-distro. Issue: I have an encrypted non-root-partition (actually /home) and the whole lifecycle of booting, working, closing works flawless. Boot and LUKS will handle the process based on crypttab and fstab, no entry in inittab. Follows the (correct) specs and works well. Except the password request. Plymouth swallows the password request. Here we do NOT talk about the initram issue - this is a slightly different situation, same bug. So solutions for similar cases do not work here. Reproducible you can try to guess when the request should be there, manually enter the matching password and the mounting goes on well. Reproducible, when you prematurely press "enter" during(!) the checking step the displayed lines shift up (and display an empty line). The password request becomes visible in this empty line after finalised checking procedure. Could probably be circumvented by adding more newline characters, it seems. So it is clearly a display issue caused by Plymouth. The request for password is fired up correctly. It is just not visible to the user. I do not have a NVIDIA in the machines I implemented it in. It's happening on laptop with Intel graphics as well as on a desktop with A10 APU graphics. Graphics card does not matter at all. I do NOT use the graphical / picture grub screen, rcS has extended verbosity. Description:Ubuntu 17.10 Release:17.10 plymouth: Installed: 0.9.2-3ubuntu17 Candidate: 0.9.2-3ubuntu17 Version table: *** 0.9.2-3ubuntu17 500 500 http://ftp.uninett.no/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 0.9.2-3ubuntu15.1 500 500 http://be.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 0.9.2-3ubuntu15 500 500 http://be.archive.ubuntu.com/ubuntu zesty/main amd64 Packages cryptsetup: Installed: 2:1.7.3-4ubuntu1 Candidate: 2:1.7.3-4ubuntu1 Version table: *** 2:1.7.3-4ubuntu1 500 500 http://ftp.uninett.no/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 2:1.7.2-0ubuntu1 500 500 http://be.archive.ubuntu.com/ubuntu zesty/main amd64 Packages ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731769 Title: No luks password prompt - plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1731769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710351] [NEW] package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
Public bug reported: crash at boot end ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-92-generic 4.4.0-92.115 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Aug 12 09:29:12 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1 HibernationDevice: RESUME=UUID=b5bbfe1e-633b-49bc-bb70-7be65b2cfff5 InstallationDate: Installed on 2016-12-10 (244 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=db3b9a2e-b503-4862-8c91-b5c5d9b50984 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 RfKill: SourcePackage: lilo Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: lilo (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710351 Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/1710351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705490] [NEW] package linux-image-extra-4.4.0-71-generic 4.4.0-71.92 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
Public bug reported: no details recognized ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-71-generic 4.4.0-71.92 ProcVersionSignature: Ubuntu 4.4.0-73.94-generic 4.4.59 Uname: Linux 4.4.0-73-generic i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp'] failed with exit code 1: Date: Sun Jun 25 10:49:38 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1 HibernationDevice: RESUME=UUID=b5bbfe1e-633b-49bc-bb70-7be65b2cfff5 InstallationDate: Installed on 2016-12-10 (221 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-73-generic root=UUID=db3b9a2e-b503-4862-8c91-b5c5d9b50984 ro quiet splash init=/sbin/upstart PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9 RfKill: SourcePackage: lilo Title: package linux-image-extra-4.4.0-71-generic 4.4.0-71.92 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: lilo (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705490 Title: package linux-image-extra-4.4.0-71-generic 4.4.0-71.92 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/1705490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322925] Re: Copy, cut, and paste in Nautilus fail in certain circumstances
In Ubuntu 17.04 I can not paste in Nautilus ("Files" 3.20.4).
- Menue item missing in right-click-contexct-menue
- no function at all using Ctrl + V
- no function at all with Shift + Insert (old Win3.1 style used to work in
older versions)
What appears: Nothing. Absolutely nothing happening.
This worked in former versions (12, 14, 15, 16.04, ...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322925
Title:
Copy, cut, and paste in Nautilus fail in certain circumstances
To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1322925/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
