Bug 2175487 - Since Kernel 6.2 my WWAN Intel XMM7560 LTE module is not working anymore
Summary: Since Kernel 6.2 my WWAN Intel XMM7560 LTE module is not working anymore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-05 09:49 UTC by Martin Wolf
Modified: 2023-04-08 01:29 UTC (History)
18 users (show)

Fixed In Version: kernel-6.2.9-300.fc38 kernel-6.2.9-200.fc37 kernel-6.2.9-100.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-02 00:16:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
full lspci XMM7560 LTE Advanced Pro Modem (4.45 KB, text/plain)
2023-03-14 00:53 UTC, Martin Wolf
no flags Details

Description Martin Wolf 2023-03-05 09:49:51 UTC
I was testing Kernel 6.2.2 from koji, when I noticed these errors after boot:

[   44.973374] iosm 0000:01:00.0: ch[1]: confused phase 2
[   45.973650] iosm 0000:01:00.0: ch[1]: confused phase 2
[   46.972517] iosm 0000:01:00.0: ch[1]: confused phase 2
[   47.973038] iosm 0000:01:00.0: ch[1]: confused phase 2
[   48.973154] iosm 0000:01:00.0: ch[1]: confused phase 3
[   49.973774] iosm 0000:01:00.0: ch[1]: confused phase 3
[   50.973899] iosm 0000:01:00.0: ch[1]: confused phase 3
[   51.972600] iosm 0000:01:00.0: ch[1]: confused phase 3
[   52.973292] iosm 0000:01:00.0: ch[1]: confused phase 3
[   53.973852] iosm 0000:01:00.0: ch[1]: confused phase 3
[   54.973506] iosm 0000:01:00.0: ch[1]: confused phase 3
[   55.974246] iosm 0000:01:00.0: ch[1]: confused phase 3
[   56.973997] iosm 0000:01:00.0: ch[1]: confused phase 3
[   57.973449] iosm 0000:01:00.0: ch[1]: confused phase 3
[   58.973716] iosm 0000:01:00.0: ch[1]: confused phase 3
[   59.972300] iosm 0000:01:00.0: ch[1]: confused phase 3
[   60.973370] iosm 0000:01:00.0: ch[1]: confused phase 3
[   61.973624] iosm 0000:01:00.0: ch[1]: confused phase 3
[   62.973746] iosm 0000:01:00.0: ch[1]: confused phase 3
[   63.972858] iosm 0000:01:00.0: ch[1]: confused phase 3
[   64.972767] iosm 0000:01:00.0: ch[1]: confused phase 3
[   65.973594] iosm 0000:01:00.0: ch[1]: confused phase 3
[   66.973674] iosm 0000:01:00.0: ch[1]: confused phase 3
[   67.973767] iosm 0000:01:00.0: ch[1]: confused phase 3
[   68.973562] iosm 0000:01:00.0: ch[1]: confused phase 3
[   69.974347] iosm 0000:01:00.0: ch[1]: confused phase 3
[   70.974073] iosm 0000:01:00.0: ch[1]: confused phase 3
[   71.972989] iosm 0000:01:00.0: ch[1]: confused phase 3
[   72.973444] iosm 0000:01:00.0: ch[1]: confused phase 3
[   73.973567] iosm 0000:01:00.0: ch[1]: confused phase 3
[   74.973770] iosm 0000:01:00.0: ch[1]: confused phase 3
[   75.974213] iosm 0000:01:00.0: ch[1]: confused phase 3
[   76.973596] iosm 0000:01:00.0: ch[1]: confused phase 3
[   77.974206] iosm 0000:01:00.0: ch[1]: confused phase 3
[   78.973950] iosm 0000:01:00.0: ch[1]: confused phase 3
[   79.973379] iosm 0000:01:00.0: ch[1]: confused phase 3
[   80.974068] iosm 0000:01:00.0: ch[1]: confused phase 3
[   81.973737] iosm 0000:01:00.0: ch[1]: confused phase 3
[   82.974208] iosm 0000:01:00.0: ch[1]: confused phase 3
[   83.972624] iosm 0000:01:00.0: ch[1]: confused phase 3
[   84.974848] iosm 0000:01:00.0: ch[1]: confused phase 3
[  129.980615] iosm 0000:01:00.0: ch[6]: confused phase 3
[  129.980752] iosm 0000:01:00.0: ch[6]: confused phase 3
[  150.002520] iosm 0000:01:00.0: ch[6]: confused phase 3
[  150.003096] iosm 0000:01:00.0: ch[6]: confused phase 3
[  150.974419] iosm 0000:01:00.0: ch[6]: confused phase 3
[  151.974468] iosm 0000:01:00.0: ch[6]: confused phase 3
[  152.974985] iosm 0000:01:00.0: ch[6]: confused phase 3
[  153.975108] iosm 0000:01:00.0: ch[6]: confused phase 3
[  154.974104] iosm 0000:01:00.0: ch[6]: confused phase 3
[  155.974429] iosm 0000:01:00.0: ch[6]: confused phase 3
[  156.974793] iosm 0000:01:00.0: ch[6]: confused phase 3
[  157.975474] iosm 0000:01:00.0: ch[6]: confused phase 3
[  158.974320] iosm 0000:01:00.0: ch[6]: confused phase 3
[  159.974456] iosm 0000:01:00.0: ch[6]: confused phase 3
[  160.975485] iosm 0000:01:00.0: ch[6]: confused phase 3
[  161.975162] iosm 0000:01:00.0: ch[6]: confused phase 3
[  162.974836] iosm 0000:01:00.0: ch[6]: confused phase 3
[  163.975702] iosm 0000:01:00.0: ch[6]: confused phase 3
[  164.975583] iosm 0000:01:00.0: ch[6]: confused phase 3
[  174.984861] iosm 0000:01:00.0: PORT open refused, phase A-CD_READY
[  174.985767] iosm 0000:01:00.0: ch[6]: confused phase 3
[  184.996879] iosm 0000:01:00.0: PORT open refused, phase A-CD_READY
[  344.482600] iosm 0000:01:00.0: msg timeout
[  344.986684] iosm 0000:01:00.0: msg timeout


they also occur on standby

[27628.054469] iosm 0000:01:00.0: msg timeout

and

[27629.718967] iosm 0000:01:00.0: PORT open refused, phase A-ROM
[27629.719417] iosm 0000:01:00.0: PORT open refused, phase A-ROM
[27629.719568] iosm 0000:01:00.0: PORT open refused, phase A-ROM
[27629.719817] iosm 0000:01:00.0: PORT open refused, phase A-ROM
[27629.719914] iosm 0000:01:00.0: PORT open refused, phase A-ROM
[27629.720005] iosm 0000:01:00.0: PORT open refused, phase A-ROM
[27629.720067] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27629.720292] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1

[27650.188429] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27650.188544] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27670.208942] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27670.209089] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27671.933355] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27672.933467] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27673.933505] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27674.933516] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27675.933507] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27676.933479] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27677.933652] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27678.933853] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27679.933618] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27680.933672] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27681.933602] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27682.933668] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27683.933834] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27684.933696] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27685.933851] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[27695.943815] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1

Comment 1 Martin Wolf 2023-03-05 10:46:17 UTC
01:00.0 Wireless controller [0d40]: Intel Corporation XMM7560 LTE Advanced Pro Modem (rev 01)
Thats the device in question.

Comment 2 Martin Wolf 2023-03-14 00:52:41 UTC
I still run into this issue with testing candidate 6.2.6:

A bit more info about the System in question:

System:
  Host: HP845G9 Kernel: 6.2.6-200.fc37.x86_64 arch: x86_64 bits: 64
    Desktop: GNOME v: 43.3 Distro: Fedora release 37 (Thirty Seven)
Machine:
  Type: Laptop System: HP product: HP EliteBook 845 14 inch G9 Notebook PC
    v: N/A serial: <superuser required>
  Mobo: HP model: 8990 v: KBC Version 09.49.00 serial: <superuser required>
    UEFI: HP v: U82 Ver. 01.04.01 date: 01/12/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 6800U with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 872 min/max: 400/4768 cores: 1: 400 2: 1186 3: 1155
    4: 1186 5: 1217 6: 400 7: 1676 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 1353 14: 400 15: 400 16: 2588

Comment 3 Martin Wolf 2023-03-14 00:53:43 UTC
Created attachment 1950375 [details]
full lspci XMM7560 LTE Advanced Pro Modem

Comment 4 Martin Wolf 2023-03-14 00:56:36 UTC
[  252.937136] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  252.937313] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  272.959103] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  272.959461] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  274.032878] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  275.032296] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  276.032547] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  277.032448] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  278.032791] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  279.032628] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  280.032501] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  281.032551] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  282.032976] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  283.032648] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  284.033002] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  285.033618] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  286.032524] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  287.032750] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  288.032786] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  298.042818] iosm 0000:01:00.0: ch[6]:invalid channel state 2,expected 1
[  337.034256] iosm 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0x0 flags=0x0000]
[  337.536467] iosm 0000:01:00.0: msg timeout
[  338.040709] iosm 0000:01:00.0: msg timeout

Comment 5 Justin M. Forbes 2023-03-14 11:35:52 UTC
Does this work with the most recent rawhide kernel?

Comment 6 Martin Wolf 2023-03-14 14:47:15 UTC
The problem still occurs with kernel-6.3.0-0.rc2.23.fc39

I will try to bisect.

Comment 7 Martin Wolf 2023-03-14 17:13:46 UTC
I am at a point where I am down to 66 commits, but I run into new issues because the module will not load properly anymore. 

I am not a bisection expert, could you give me a hint how to circumvent this issue?

Comment 8 Martin Wolf 2023-03-15 21:59:20 UTC
After bisecting the issue I found that this commit causes it:
d08b0f8f46e45a274fc8c9a5bc92cb9da70d9887 is the first bad commit
commit d08b0f8f46e45a274fc8c9a5bc92cb9da70d9887
Author: Shane Parslow <shaneparslow808>
Date:   Sat Oct 29 02:03:56 2022 -0700

    net: wwan: iosm: add rpc interface for xmm modems
    
    Add a new iosm wwan port that connects to the modem rpc interface. This
    interface provides a configuration channel, and in the case of the 7360, is
    the only way to configure the modem (as it does not support mbim).
    
    The new interface is compatible with existing software, such as
    open_xdatachannel.py from the xmm7360-pci project [1].
    
    [1] https://github.com/xmm7360/xmm7360-pci
    
    Signed-off-by: Shane Parslow <shaneparslow808>
    Reviewed-by: Loic Poulain <loic.poulain>
    Signed-off-by: David S. Miller <davem>

 drivers/net/wwan/iosm/iosm_ipc_chnl_cfg.c | 2 +-
 drivers/net/wwan/wwan_core.c              | 4 ++++
 include/linux/wwan.h                      | 2 ++
 3 files changed, 7 insertions(+), 1 deletion(-)

This commit aims for a different XMM modem (7360) other than the one I use (7560).

Would it be possible, that you revert that commit until intel / upstream has fixed it?

Comment 9 Justin M. Forbes 2023-03-16 14:39:38 UTC
Thorsten picked this up in the upstream regression tracker this morning, and tends to get quick results. I will keep an eye on it and make some decision soon, but likely not in time for 6.2.7 or even 6.2.8 depending on upstream.

Comment 10 Martin Wolf 2023-03-16 15:11:35 UTC
I noticed, thank you for the help!

Please feel free to push kernel 6.2 to stable, until it is fixed I will blacklist iosm.

Comment 11 Martin Wolf 2023-03-28 08:53:09 UTC
would it be possible, that you include this patch here to fix it?
https://lore.kernel.org/all/b5b3b67ed4dcbc508961dfd3e196857d6ae1385c.1679983314.git.m.chetan.kumar@intel.com/

Comment 12 Hans de Goede 2023-03-29 11:44:13 UTC
(In reply to Martin Wolf from comment #11)
> would it be possible, that you include this patch here to fix it?
> https://lore.kernel.org/all/b5b3b67ed4dcbc508961dfd3e196857d6ae1385c.
> 1679983314.git.m.chetan.kumar/

Thank you for pointing out there is a fix for this. I have created a MR to get this fix added to the Fedora 6.2 kernel builds:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2382

Justin, note as mentioned in the merge-request this patch has already been accepted upstream in -next.

Comment 13 Fedora Update System 2023-03-31 19:46:28 UTC
FEDORA-2023-c46eb02bbf has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c46eb02bbf

Comment 14 Fedora Update System 2023-03-31 19:53:10 UTC
FEDORA-2023-98251cef79 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-98251cef79

Comment 15 Fedora Update System 2023-03-31 19:53:11 UTC
FEDORA-2023-d525cf5272 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d525cf5272

Comment 16 Fedora Update System 2023-04-01 01:34:13 UTC
FEDORA-2023-c46eb02bbf has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c46eb02bbf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 17 Fedora Update System 2023-04-01 02:11:37 UTC
FEDORA-2023-d525cf5272 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d525cf5272`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d525cf5272

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2023-04-01 02:17:06 UTC
FEDORA-2023-98251cef79 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-98251cef79`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-98251cef79

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 19 Fedora Update System 2023-04-02 00:16:33 UTC
FEDORA-2023-c46eb02bbf has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2023-04-05 01:35:20 UTC
FEDORA-2023-98251cef79 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 21 Fedora Update System 2023-04-08 01:29:33 UTC
FEDORA-2023-d525cf5272 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


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