https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #20 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=923e7f7e12670e97b097a195e69c848a6e8773a2
commit 923e7f7e12670e97b097a195e69c848a6e8773a2
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254478
--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=c80a4b76ceacc5aab322e7ac1407eea8c90cb3b1
commit c80a4b76ceacc5aab322e7ac1407eea8c90cb3b1
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #12 from Maxim Shalomikhin ---
I have one machine with hanging sysct:
99750 - D 22:33.32 /sbin/sysctl net.inet.tcp.hostcache.list
# procstat -kk 99750
PIDTID COMMTDNAME KSTACK
99750
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #13 from Richard Scheffenegger ---
Thanks. I can not comment as to why the hostcache.count counts up and beyond
the limit.
But the other data confirms that what you are seeing is the (unsuccessful)
attempt in allocating a huge
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235700
Ryan Moeller changed:
What|Removed |Added
CC||freql...@freebsd.org
--- Comment #6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235700
Ryan Moeller changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235700
Ryan Moeller changed:
What|Removed |Added
Flags|mfc-stable12?, |mfc-stable12+,
|m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #14 from Michael Tuexen ---
I agree with Richard that we know he issue and the patches from Richard should
address the problem.
However, I would like to understand why net.inet.tcp.hostcache.count >
net.inet.tcp.hostcache.cache
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #15 from Michael Tuexen ---
Could you also post for the output of netstat -sptcp the two lines with
counters for hostcache entries added and bucket overflow.
--
You are receiving this mail because:
You are on the CC list for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #16 from Michael Tuexen ---
Please note that you should not be able to set the
net.inet.tcp.hostcache.cachelimit too high. It is set automatically to
net.inet.tcp.hostcache.bucketlimit * net.inet.tcp.hostcache.hashsize and you
s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #17 from Richard Scheffenegger ---
net.inet.tcp.hostcache.count: 4294966447 is -849 (decimal).
tcp_hc_purge_internal decrements hostcache.count unconditionally, and would be
the most likely candidate where that counter can rap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #18 from Michael Tuexen ---
(In reply to Richard Scheffenegger from comment #17)
But tcp_hc_purge_internal() decrements the counter when it removes an entry and
frees it. I double checked the code and I think the counter is hand
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #19 from Richard Scheffenegger ---
(In reply to Michael Tuexen from comment #18)
> Richard: Do you see a way how the counter could be off?
Unfortunately not. I was thinking about adding KASSERTS when the counter is
about to be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333
--- Comment #20 from Michael Tuexen ---
(In reply to Richard Scheffenegger from comment #19)
As far as I can see, it is impossible to change the cache config at runtime,
the relevant variables are all only settable in /boot/loader.conf.
No
Hi Özkan,
I'm glad that worked.
Nevertheless, there must be an issue lurking around in the ixl driver code,
affecting the case enable_head_writeback==1.
It may be related to the fact that https://reviews.freebsd.org/D26896
causes issues, even though it looks a legitimate change.
Cheers,
Vincen
15 matches
Mail list logo
