Bug 2139279 - [abrt] ModemManager: g_malloc0(): ModemManager killed by SIGABRT
Summary: [abrt] ModemManager: g_malloc0(): ModemManager killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 37
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Davide Cavalca
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:8b56bffb43e3f70db8213a02ba1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-02 04:49 UTC by Joerg Skottke
Modified: 2023-12-05 23:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-05 23:33:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.37 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: core_backtrace (17.45 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: cpuinfo (2.78 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: dso_list (639 bytes, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: environ (287 bytes, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: limits (1.29 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: maps (3.89 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: mountinfo (3.77 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: open_fds (921 bytes, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: proc_pid_status (1.35 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details
File: var_log_messages (1.91 KB, text/plain)
2022-11-02 04:49 UTC, Joerg Skottke
no flags Details

Description Joerg Skottke 2022-11-02 04:49:16 UTC
Version-Release number of selected component:
ModemManager-1.18.8-2.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/system.slice/ModemManager.service
cmdline:        /usr/sbin/ModemManager
crash_function: g_malloc0
executable:     /usr/sbin/ModemManager
journald_cursor: s=15d393fc27df42ef8a3f49c68849829d;i=1b17b;b=c4ba2a66ede24c5e860982d3a23faaf8;m=384a537;t=5eb5d4a1c117d;x=b649a8d1e83ab50b
kernel:         5.19.13-300.fc37.x86_64
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            0

Comment 1 Joerg Skottke 2022-11-02 04:49:19 UTC
Created attachment 1921609 [details]
File: backtrace

Comment 2 Joerg Skottke 2022-11-02 04:49:20 UTC
Created attachment 1921610 [details]
File: core_backtrace

Comment 3 Joerg Skottke 2022-11-02 04:49:21 UTC
Created attachment 1921611 [details]
File: cpuinfo

Comment 4 Joerg Skottke 2022-11-02 04:49:22 UTC
Created attachment 1921612 [details]
File: dso_list

Comment 5 Joerg Skottke 2022-11-02 04:49:23 UTC
Created attachment 1921613 [details]
File: environ

Comment 6 Joerg Skottke 2022-11-02 04:49:24 UTC
Created attachment 1921614 [details]
File: limits

Comment 7 Joerg Skottke 2022-11-02 04:49:26 UTC
Created attachment 1921615 [details]
File: maps

Comment 8 Joerg Skottke 2022-11-02 04:49:27 UTC
Created attachment 1921616 [details]
File: mountinfo

Comment 9 Joerg Skottke 2022-11-02 04:49:28 UTC
Created attachment 1921617 [details]
File: open_fds

Comment 10 Joerg Skottke 2022-11-02 04:49:29 UTC
Created attachment 1921618 [details]
File: proc_pid_status

Comment 11 Joerg Skottke 2022-11-02 04:49:30 UTC
Created attachment 1921619 [details]
File: var_log_messages

Comment 12 Benjamin Masse 2022-11-19 19:43:08 UTC
Similar problem has been detected:

Updated to Fedora 37.
Not actually using a modem nor a SIM.

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/system.slice/ModemManager.service
cmdline:        /usr/sbin/ModemManager
crash_function: g_malloc0
executable:     /usr/sbin/ModemManager
journald_cursor: s=cec8d04ea4cd44db96b2ae72a1513954;i=55517;b=76c9bc2b0f074413ace5d0b7113c8a0b;m=bb23c3d8;t=5edd7240346a4;x=66a44aa8c7069513
kernel:         6.0.8-300.fc37.x86_64
package:        ModemManager-1.18.8-2.fc37
reason:         ModemManager killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Tao Jin 2022-11-19 19:50:12 UTC
Just FYI, response from the maintainer

https://pagure.io/fesco/issue/2888

Comment 14 Markus Weller 2022-12-01 19:29:36 UTC
Similar problem has been detected:

A crash of the gsm driver occurs when the laptop is suspended (with the Legacy Linux Method and the "Linux and Windows")
This  crash wakes up the Laptop again

[  260.192990] printk: Suspending console(s) (use no_console_suspend to debug)
[  261.533707] ishtp {C1CC78B9-B693-4E54-9191-5169CB027C25}: PM: parent 0000:00:12.0 should not be sleeping
[  261.533780] ishtp {1F050626-D505-4E94-B189-535D7DE19CF2}: PM: parent 0000:00:12.0 should not be sleeping
[  261.533803] ishtp {BB579A2E-CC54-4450-B1D0-5E7520DCAD25}: PM: parent 0000:00:12.0 should not be sleeping
[  261.533820] ishtp {28536C54-CF99-4F27-A6F3-499741BAADFE}: PM: parent 0000:00:12.0 should not be sleeping
[  261.534240] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=4
[  263.137434] mtk_t7xx 0000:08:00.0: [PM] SAP suspend error: -110
[  263.137501] mtk_t7xx 0000:08:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
[  263.137539] mtk_t7xx 0000:08:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -110
[  263.137558] mtk_t7xx 0000:08:00.0: PM: failed to suspend async: error -110
[  263.138001] PM: Some devices failed to suspend, or early wake event detected

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/system.slice/ModemManager.service
cmdline:        /usr/sbin/ModemManager
crash_function: g_malloc0
executable:     /usr/sbin/ModemManager
journald_cursor: s=d3a7f7841e3d4842bc05938ec791c84b;i=a1eb;b=dd266826e61d4d3ea5f491de2bfb0046;m=3815bd9;t=5eec8b2f62187;x=5c2ae98a08e7b762
kernel:         6.0.9-300.fc37.x86_64
package:        ModemManager-1.18.8-2.fc37
reason:         ModemManager killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 15 Alexander Haas 2023-01-05 07:54:08 UTC
Similar problem has been detected:

I get this bug reported since 5 days after every boot. As I don't use the Modem in my notebook (didn't even knew it had one), I'm not directly affected, but it could of course help to fix it.

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/system.slice/ModemManager.service
cmdline:        /usr/sbin/ModemManager
crash_function: g_malloc0
executable:     /usr/sbin/ModemManager
journald_cursor: s=794ad996433b45b190c31cb6a8bd3989;i=a025;b=10e30e9dfe67413da50a7a97c6f76eed;m=29d0d4c;t=5f107474a1820;x=74adecde693ad5b3
kernel:         6.0.15-300.fc37.x86_64
package:        ModemManager-1.18.8-2.fc37
reason:         ModemManager killed by SIGABRT
rootdir:        /
runlevel:       unknown
type:           CCpp
uid:            0

Comment 16 Fedora Admin user for bugzilla script actions 2023-02-21 12:04:25 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 17 Fedora Admin user for bugzilla script actions 2023-02-22 00:03:55 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 18 Aoife Moloney 2023-11-23 00:28:29 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 19 Aoife Moloney 2023-12-05 23:33:04 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.