New: NETDEV WATCHDOG: wwan0 (cdc_ncm): transmit queue 0 timed out

https://bugzilla.kernel.org/show_bug.cgi?id=218356

            Bug ID: 218356
           Summary: NETDEV WATCHDOG: wwan0 (cdc_ncm): transmit queue 0
                    timed out
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 305689
--> https://bugzilla.kernel.org/attachment.cgi?id=305689&action=edit
usb3.0 usbnet crash log

I am using Linux kernel version 5.10.110 and the USB 3.0 interface. During the USB device packet filling test, after running for a period of time, an error message NETDEV WATCHLOG: wwan0 (cdc-ncm): transmit queue 0 timed out was reported. The analysis shows that the print log exceeds the threshold dev ->txq.qlen>=TX_ QLEN (dev), how to solve this problem

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

5.10.110 is a very old and obsolete kernel version, having been released over a year and a half ago.

Please try a newer kernel release, the latest 5.10.y release is 5.10.206, but really, can you try 6.7 to see if this issue has been resolved by now?

thanks,

greg k-h

https://bugzilla.kernel.org/show_bug.cgi?id=218356

--- Comment #1 from Greg Kroah-Hartman ([email protected]) ---

5.10.110 is a very old and obsolete kernel version, having been released over a year and a half ago.

Please try a newer kernel release, the latest 5.10.y release is 5.10.206, but really, can you try 6.7 to see if this issue has been resolved by now?

thanks,

greg k-h

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=218356

--- Comment #2 from yilei ([email protected]) ---
Thank you very much for your reply. I have tested the firmware of buildroot and its kernel version is 4.19.225. This version should not have this issue, but I am currently using the firmware of friendlyWrt and its kernel version is 5.10.110. This version must have this issue. I suspect that buildroot has any patches that have already fixed this issue. Should I consult with the official friendlyWrt？

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.