linux-kernel - Re: [PATCH v3 11/11] arm64: dts: qcom: sdm845-lg-common: Change ipa gsi-loader to 'self'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0d98d501-85cd-4647-8d1f-126242c220a5@oss.qualcomm.com>
Date: Mon, 1 Dec 2025 13:54:04 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Paul Sajna <sajattack@...tmarketos.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
 <conor+dt@...nel.org>, David Heidelberg <david@...t.cz>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, phone-devel@...r.kernel.org,
        Amir Dahan <system64fumo@...tonmail.com>,
        Christopher Brown <crispybrown@...il.com>
Subject: Re: [PATCH v3 11/11] arm64: dts: qcom: sdm845-lg-common: Change ipa
 gsi-loader to 'self'

On 11/25/25 5:29 AM, Paul Sajna wrote:
> October 1, 2025 at 9:11 AM, "Konrad Dybcio" <konrad.dybcio@....qualcomm.com mailto:konrad.dybcio@....qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E > wrote:
> 
> 
>>
>> On 9/29/25 7:05 AM, Paul Sajna wrote:
>>
>>>
>>> This lets modem get a bit closer to working
>>>
>> What prevents it from working? Does it crash? Has rmtfs started?
>> Does `rmtfs -vP` print any warnings?
>>
>> Konrad
>>
> 
> <msg> [modem0] state changed (unknown -> locked)
> <wrn> [modem0] modem couldn't be initialized: Couldn't check unlock status: Couldn't get SIM lock status after 30 retries
> <msg> [modem0] state changed (locked -> failed)
> <wrn> [modem0] couldn't load SUPL server: Failed to receive indication with the current server settings
> <wrn> [modem0] couldn't load supported assistance data types: Failed to receive indication with the predicted orbits data source
> <wrn> [modem0] couldn't build device ids: Unknown device subsystem
> <wrn> [device qcom-soc] error initializing: Modem in failed state: sim-missing

IDK if it's super related, but some phones have additional mechanisms
for detecting (particulary the secondary) SIM - any chance yours is a
dual-SIM and you can try using the other slot?

Konrad