On Sat, 13 Mar 2021 at 23:24, Özkan KIRIK wrote:
>
> Hello Adrian,
>
> I wonder if the current RSS code supports software mode. Is it possible to
> enforce software RSS? And what about Sender Side Scaling ?
The current RSS code does enforce it on all the NICs, so if you enable
it and you don't h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254159
Kubilay Kocak changed:
What|Removed |Added
CC||n...@freebsd.org
UR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203916
Kubilay Kocak changed:
What|Removed |Added
Resolution|FIXED |Overcome By Events
--- Comment #5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983
Kubilay Kocak changed:
What|Removed |Added
Flags||maintainer-feedback?(shurd@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
Kubilay Kocak changed:
What|Removed |Added
Summary|[if_bridge] Panic when |if_bridge: Panic when using
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
--- Comment #1 from shamaz.ma...@gmail.com ---
Here is another backtrace from 13.0-RC3:
(kgdb) bt
#0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1 doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Kubilay Kocak changed:
What|Removed |Added
Flags||mfc-stable13+,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #11 from Aleks ---
(In reply to Alexander V. Chernikov from comment #9)
p.s. I can't make him write dump file after I compiled custom kernel
(+FIB_ALGO)
When I test dumps with "sysctl debug.kdb.panic=1" the dump is written but w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #10 from Aleks ---
(In reply to Alexander V. Chernikov from comment #9)
by core dump you mean vmcore.* file?
p.s. I can even give you access to this server if it will help you (it's not in
production)
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #9 from Alexander V. Chernikov ---
Obvious code checks and tries to repro this in an easy way failed - I don’t
have a good idea on why its happening. Setting up multiple live bgp feeds will
take some time, so there are multiple
Youssef GHORBAL wrote:
>Hi Jason,
>
>> On 17 Mar 2021, at 18:17, Jason Breitman
>> wrote:
>>
>> Please review the details below and let me know if there is a setting that I
>> should apply to my FreeBSD NFS Server or if there is a bug fix that I can
>> apply to resolve my issue.
>> I shared t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #8 from Aleks ---
(In reply to Alexander V. Chernikov from comment #7)
Sure, just tell me what you mean by "share kernel&core"
--
You are receiving this mail because:
You are on the CC list for the bug.
___
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #7 from Alexander V. Chernikov ---
(In reply to Aleks from comment #5)
Is there any chance you could share kernel&core?
--
You are receiving this mail because:
You are on the CC list for the bug.
__
Thanks for sharing as this sounds exactly like my issue.
I had implemented the change below on 3/8/2021 and have experienced the NFS
hang after that.
Do I need to reboot or umount / mount all of the clients and then I will be ok?
I had not rebooted the clients, but would to get out of this situa
The issue did trigger again.
I ran the script below for ~15 minutes and hope this gets you what you need.
Let me know if you require the full output without grepping nfsd.
#!/bin/sh
while true
do
/bin/date >> /tmp/nfs-hang.log
/bin/ps axHl | grep nfsd | grep -v grep >> /tmp/nfs-hang.log
16 matches
Mail list logo
