linux-kernel - Re:Re: [Bug 215433] New: data connection lost on Qualcomm SDX55 PCIe device

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: <7d8532a3.2314.17e09457a76.Coremail.slark_xiao@163.com>
Date:   Thu, 30 Dec 2021 10:57:35 +0800 (CST)
From:   "Slark Xiao" <slark_xiao@....com>
To:     "Bjorn Helgaas" <helgaas@...nel.org>
Cc:     bjorn@...gaas.com, linux-pci@...r.kernel.org,
        "Loic Poulain" <loic.poulain@...aro.org>,
        "Sergey Ryazanov" <ryazanov.s.a@...il.com>,
        "Johannes Berg" <johannes@...solutions.net>,
        "Manivannan Sadhasivam" <mani@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re:Re: [Bug 215433] New: data connection lost on Qualcomm SDX55
 PCIe device

















At 2021-12-30 01:46:05, "Bjorn Helgaas" <helgaas@...nel.org> wrote:
>[+cc MHI folks]
>
>On Tue, Dec 28, 2021 at 11:26:02AM +0000, bugzilla-daemon@...zilla.kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=215433
>> 
>>            Summary: data connection lost on Qualcomm SDX55 PCIe device
>>     Kernel Version: 5.13.0,5.15.0
>> ...
>
>> For Qualcomm based modem devices, with PCIE interface, and mhi driver based on
>> kernel 5.13.0, it will lose data connection. Details as below:
>> 
>>     Phenomenon:
>>         1) Can NOT connect to Internet
>>         2) /dev/wwan0p1QCDM, /dev/wwan0p2MBIM, /dev/wwan0p3AT NOT response
>> 
>>     Reproduce steps
>>         1) Connect Internet via cellular
>>         2) Do speedtest(https://www.speedtest.net/) or download a 1GB file
>> (ipv4.download.thinkbroadband.com/1GB.zip)
>> 
>>     Recovery method
>>         Only can be recovered by reboot host
>> 
>>     Others
>>         It can NOT be reproduced in Windows 10/11.
>
>Thanks very much for the report.  I'm not familiar with the mhi
>driver, so I added some folks who might be.
>
>Can you please collect the complete dmesg log and output of
>"sudo lspci -vv" and attach both to the bugzilla?
>
>Does the network connection work for a while, then stop working?  If
>so, is there anything logged in the dmesg log when it stops working?
>
>Do you know of any Linux versions that do not have this problem?  If
>it used to work but it got broken, that would help narrow things down.
>
>Thanks,
>  Bjorn

Hi Bjorn,
   Related log has been uploaded.
   
   Yes, the time before stop working may less than 1 minutes, or more than 15 minutes. Finally, it would stop working.
 There is no message would be reported in dmesg log with default log level. So I think this is a situation that we all may miss it.
We also tried to add some debug log. But no findings.
   As we add support our device in v5.12(more or less), so we didn't test it with previous version. 
Actually this issue is found in both v5.13 and v5.15 official release.
   
   BTW, there is some other vendor also report this issue, like Quectel SDX24 module. 
So I believe this is a common issue for all mhi device.
 
Thanks
 Slark