From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 218536] New: divide error in tcp_rcv_space_adjust
Date: Tue, 27 Feb 2024 11:07:40 -0800 [thread overview]
Message-ID: <20240227110740.0f657fbe@hermes.local> (raw)
Begin forwarded message:
Date: Tue, 27 Feb 2024 18:16:35 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 218536] New: divide error in tcp_rcv_space_adjust
https://bugzilla.kernel.org/show_bug.cgi?id=218536
Bug ID: 218536
Summary: divide error in tcp_rcv_space_adjust
Product: Networking
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: stephen@networkplumber.org
Reporter: adam@mizerski.pl
Regression: No
Created attachment 305916
--> https://bugzilla.kernel.org/attachment.cgi?id=305916&action=edit
dmesg
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:
<TASK>
? 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
tcp_recvmsg_locked+0x2c3/0x950
tcp_recvmsg+0x73/0x1f0
? __pfx_pollwake+0x10/0x10
inet_recvmsg+0x56/0x130
? security_socket_recvmsg+0x41/0x70
sock_recvmsg+0xa6/0xd0
__sys_recvfrom+0xaa/0x120
? 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
__x64_sys_recvfrom+0x24/0x30
do_syscall_64+0x61/0xe0
entry_SYSCALL_64_after_hwframe+0x6e/0x76
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2024-02-27 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240227110740.0f657fbe@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).