Bug 1795345

Summary: ModemManager fail to start on CompulLab Fitlet2 with attached gsm card: trap in libglib-2.0
Product: [Fedora] Fedora Reporter: nicolasoliver03
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dcbw, dwalsh, fgiudici, grepl.miroslav, lkundrak, lvrabec, plautrba, pwhalen, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-02 09:51:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1269538    
Attachments:
Description Flags
Output of journalctl --unit ModemManager.service none

Description nicolasoliver03 2020-01-27 18:14:46 UTC 
Created attachment 1655736 [details]
Output of journalctl --unit ModemManager.service

Description of problem:

ModemManager fail to start on CompulLab Fitlet2 with attached gsm card


Version-Release number of selected component (if applicable):

[root@fedora-iot-2 ~]# rpm -qa ModemManager
ModemManager-1.10.8-1.fc32.x86_64

[root@fedora-iot-2 ~]# rpm-ostree status
State: idle
AutomaticUpdates: disabled
Deployments:
* ostree://fedora-iot:fedora/rawhide/x86_64/iot
                   Version: 32.20200126.0 (2020-01-26T16:42:34Z)
                BaseCommit: 0095fc7f49c7f794f12bfa572c374df939e18b62ae232872f351951dc8e163bc
              GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0
           LayeredPackages: cockpit cockpit-ostree cockpit-selinux


How reproducible:
Install Fedora IoT Rawhide in Compulab Fitlet2 with GSM module, and boot it


Steps to Reproduce:
1. Install F32 Rawhide
2. Boot
3. systemctl status ModemManager

Actual results:

[root@fedora-iot-2 ~]# systemctl status ModemManager
● ModemManager.service - Modem Manager
     Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Mon 2020-01-27 09:56:53 PST; 13min ago
    Process: 1264 ExecStart=/usr/sbin/ModemManager (code=killed, signal=TRAP)
   Main PID: 1264 (code=killed, signal=TRAP)

Jan 27 09:56:53 fedora-iot-2 systemd[1]: ModemManager.service: Scheduled restart job, restart counter is at 10.
Jan 27 09:56:53 fedora-iot-2 systemd[1]: Stopped Modem Manager.
Jan 27 09:56:53 fedora-iot-2 systemd[1]: ModemManager.service: Start request repeated too quickly.
Jan 27 09:56:53 fedora-iot-2 systemd[1]: ModemManager.service: Failed with result 'signal'.
Jan 27 09:56:53 fedora-iot-2 systemd[1]: Failed to start Modem Manager.

Expected results:

Status Success.

Additional info:

Already had problems before with GSM, but was initial-setup.service https://bugzilla.redhat.com/show_bug.cgi?id=1755580 

Attached journal output for server

dmesg shows the following

[root@fedora-iot-2 ~]# dmesg | grep Modem
[   25.320771] traps: ModemManager[832] trap int3 ip:7fd595a3fe05 sp:7fd594be5b40 error:0 in libglib-2.0.so.0.6304.0[7fd595a04000+84000]
Comment 1 Paul Whalen 2020-01-31 18:19:21 UTC 
This looks like an selinux issue, AVC's below:

ime->Fri Jan 31 12:58:18 2020
type=AVC msg=audit(1580493498.551:74): avc:  denied  { setsched } for  pid=833 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=0
----
time->Fri Jan 31 12:58:20 2020
type=AVC msg=audit(1580493500.653:90): avc:  denied  { setsched } for  pid=893 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=0
----
time->Fri Jan 31 12:58:22 2020
type=AVC msg=audit(1580493502.234:101): avc:  denied  { setsched } for  pid=914 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=0
----
time->Fri Jan 31 12:58:24 2020
type=AVC msg=audit(1580493504.345:139): avc:  denied  { setsched } for  pid=984 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=0
----
time->Fri Jan 31 12:58:25 2020
type=AVC msg=audit(1580493505.975:147): avc:  denied  { setsched } for  pid=1021 comm="ModemManager" scontext=system_u:system_r:modemmanager_t:s0 tcontext=system_u:system_r:modemmanager_t:s0 tclass=process permissive=0


[root@fitlet2 ~]# setenforce 0
[root@fitlet2 ~]# systemctl restart ModemManager
[root@fitlet2 ~]# systemctl status ModemManager
● ModemManager.service - Modem Manager
     Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2020-01-31 13:13:53 EST; 5s ago
   Main PID: 1122 (ModemManager)
      Tasks: 7 (limit: 9216)
     Memory: 8.2M
        CPU: 897ms
     CGroup: /system.slice/ModemManager.service
             ├─1122 /usr/sbin/ModemManager
             └─1129 /usr/libexec/qmi-proxy
Comment 2 Lukas Vrabec 2020-02-02 09:51:34 UTC 

*** This bug has been marked as a duplicate of bug 1795524 ***