Bug 218536 - divide error in tcp_rcv_space_adjust
Summary: divide error in tcp_rcv_space_adjust
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: Stephen Hemminger
Depends on:
Reported: 2024-02-27 18:16 UTC by Adam Mizerski
Modified: 2024-03-28 13:54 UTC (History)
2 users (show)

See Also:
Kernel Version:
Regression: No
Bisected commit-id:

dmesg (7.11 KB, text/plain)
2024-02-27 18:16 UTC, Adam Mizerski

Description Adam Mizerski 2024-02-27 18:16:35 UTC
Created attachment 305916 [details]

Kernel: 6.7.6 from openSUSE Tumbleweed (but I noticed it happening earlier as well, not sure since when)

Network card:
Bus 002 Device 005: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet

Reproducible: Happens maybe once a day or few days. Don't know how and why.

Symptoms: Firefox stops being able to make any network connections. I need to kill it, because it's stuck even when closing. Everything else seems to be working fine (including stuff like https://github.com/debauchee/barrier).

Call Trace:
 ? die+0x36/0x90
 ? do_trap+0xda/0x100
 ? tcp_rcv_space_adjust+0xbe/0x160
 ? do_error_trap+0x6a/0x90
 ? tcp_rcv_space_adjust+0xbe/0x160
 ? exc_divide_error+0x38/0x50
 ? tcp_rcv_space_adjust+0xbe/0x160
 ? asm_exc_divide_error+0x1a/0x20
 ? tcp_rcv_space_adjust+0xbe/0x160
 ? tcp_rcv_space_adjust+0x1a/0x160
 ? __pfx_pollwake+0x10/0x10
 ? security_socket_recvmsg+0x41/0x70
 ? switch_fpu_return+0x50/0xe0
 ? syscall_exit_to_user_mode+0x2b/0x40
 ? do_syscall_64+0x70/0xe0
 ? do_syscall_64+0x70/0xe0
 ? syscall_exit_to_user_mode+0x2b/0x40
Comment 1 igo9586 2024-03-16 15:56:53 UTC
I also encountered this bug. (division by zero in tcp_rcv_space_adjust)

I am using Arch Linux with vanilla kernel.

I think it started happening when upgraded when I upgraded from kernel 6.5.7 to 6.6.1 but was definitely around when I upgraded to 6.6.5 based on the Firefox crash reports I have.

It can also happen to slirp4netns when running with rootless podman.

However, this is definitely adapter dependent.

I have two USB AX88179 Gigabit Ethernet devices.

It only happens with my old Trendnet TU3-ETG v1.0R but I got a new Tp-Link UE300C and I have not encountered this issue at all.

The old Trendnet device was acting weird even before this bug. For example, it only worked with certain USB ports.
Comment 2 comio 2024-03-28 13:54:20 UTC
I can confirm same issue and same hw ASIX AX88179.



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