[Touch-packages] [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 Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1970093 Title: interface status communication fails: state UNKNOWN persists for GSM- modem Sierra Wireless EM7421 Status in network-manager package in Ubuntu: New Bug description: 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:
[Touch-packages] [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 Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1970086 Title: GSM modem does not work properly (driver / config issue) Status in libmbim package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1970086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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:
[Touch-packages] [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 Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1969241 Title: Network issue no IPv6 using Sierra Wireless EM7421 and mbim Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: 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
[Touch-packages] [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
[Touch-packages] [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
[Touch-packages] [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
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1956845 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: 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)
[Touch-packages] [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:
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1954956 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: 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
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1944122 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: 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'
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1940781 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: 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:
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1940781 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: 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
[Touch-packages] [Bug 1940690] Re: Xorg crash
this is a duplicate of #1939417. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1940690 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: [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:
[Touch-packages] [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
[Touch-packages] [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 Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Expected result: when opening laptop lid the lock screen presents itself so I can unlock my session Actual result: the contents of my desktop are visible (windows, etc) and I can move my mouse cursor around but I cannot interact with the desktop session at all. Hovering over UI elements or clicking them has no effect. In order to get the login prompt I have to ctrl+alt+f1, login at the console, and run sudo systemctl restart lightdm, then I can login normally and resume whatever I was doing from before I closed the laptop lid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 23 09:08:32 2019 InstallationDate: Installed on 2019-11-09 (14 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to openssh in 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 Status in openssh package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1823474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1801805 Title: pdf printer provided by cups-pdf has disappeared since update to 18.04 Status in cups package in Ubuntu: New Bug description: 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
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1436168 Title: systemd-journald crashed with SIGABRT in journal_file_move_to_object() Status in systemd package in Ubuntu: Invalid Bug description: Crashed over night while recovering backup. . Xubuntu 15.04 beta1 ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 Date: Tue Mar 24 23:13:27 2015 ExecutablePath: /lib/systemd/systemd-journald ExecutableTimestamp: 1427124595 InstallationDate: Installed on 2015-03-23 (1 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcCmdline: /lib/systemd/systemd-journald ProcCwd: / ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=45370e47-0377-4e9d-87fc-81889c091532 ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: systemd-journald crashed with SIGABRT UpgradeStatus: Upgraded to vivid on 2015-03-24 (0 days ago) UserGroups: dmi.bios.date: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1436168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
