[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341 --- Comment #10 from Eric Joyner --- Also, why is igb0 using MSI, but igb1 is using MSI-X? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org

[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341 --- Comment #9 from VVD --- (In reply to Vladislav Shabanov from comment #8) bge or igb??? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org

[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341 --- Comment #8 from Vladislav Shabanov --- Bad news: At 15:00 I turned off all options (-rxcsum -rxcsum6 ...) and left the machine alone. At 20:05 the NIC hung again. Now I can reproduce the hung using sequence of ifconfig bge0 txcsum

[Bug 251570] Release script passes CPUTYPE variable to both host and target build from MAKE_CONF file

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251570 --- Comment #12 from Mark Millard --- See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254319 for a change that was made to allow distinctions between the CHROOT_* and RELEASE_* related build activities. The comments cover some abou

[Bug 254367] etcupdate status should exit with rc != 0 whenever there is one or more conflicts

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254367 Bug ID: 254367 Summary: etcupdate status should exit with rc != 0 whenever there is one or more conflicts Product: Base System Version: CURRENT Hardware: Any

[Bug 251570] Release script passes CPUTYPE variable to both host and target build from MAKE_CONF file

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251570 daniel.engberg.li...@pyret.net changed: What|Removed |Added Resolution|FIXED |Not A Bug -- You

[Bug 251570] Release script passes CPUTYPE variable to both host and target build from MAKE_CONF file

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251570 daniel.engberg.li...@pyret.net changed: What|Removed |Added Resolution|--- |FIXED

[Bug 254366] Severe IPv6 TCP transfer issues on 13.0-RC2 with virtio network adapter

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254366 --- Comment #4 from Michael Tratz --- Created attachment 223369 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223369&action=edit dmesg Also it doesn't matter if the machine configuration is q35 or i440fx. -- You are receiving

[Bug 254366] Severe IPv6 TCP transfer issues on 13.0-RC2 with virtio network adapter

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254366 --- Comment #3 from Michael Tratz --- Created attachment 223368 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223368&action=edit ifconfig defaults on FreeBSD 13.0-RC2 virtio -- You are receiving this mail because: You are the

[Bug 254366] Severe IPv6 TCP transfer issues on 13.0-RC2 with virtio network adapter

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254366 --- Comment #2 from Michael Tratz --- Created attachment 223367 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223367&action=edit iperf3 ipv6 with ifconfig vtnet0 -tso6 FreeBSD 13.0-RC2 -- You are receiving this mail because: Y

[Bug 254366] Severe IPv6 TCP transfer issues on 13.0-RC2 with virtio network adapter

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254366 --- Comment #1 from Michael Tratz --- Created attachment 223366 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223366&action=edit iperf3 transfer speed ipv4 on FreeBSD 13.0-RC2 -- You are receiving this mail because: You are th

[Bug 254366] Severe IPv6 TCP transfer issues on 13.0-RC2 with virtio network adapter

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254366 Bug ID: 254366 Summary: Severe IPv6 TCP transfer issues on 13.0-RC2 with virtio network adapter Product: Base System Version: 13.0-STABLE Hardware: amd64

[Bug 210432] vt(4) does not support boot time splash screen

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210432 --- Comment #7 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/doc/commit/?id=ecc2b1a6a0c0979474f6bdb2c59cafbaa33dd958 commit ecc2b1a6a0c0979474f6bdb2c59cafbaa33dd958 Author:

[Bug 232397] ctld does not depend on sysctl.conf being evaluated

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232397 --- Comment #6 from Mark Linimon --- (In reply to Pete French from comment #5) [Speaking for myself here, not as bugmeister@] I will repeat my usual claim that the "Affects" setting is ... ah ... merely decorative. In an organization that

[Bug 232397] ctld does not depend on sysctl.conf being evaluated

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232397 --- Comment #5 from Pete French --- BTW, having the bug as "affects only me" is a bit of a mischaracterisation, as this will affect anyone who only wants ctld to listen on a specific IP address wont it ? -- You are receiving this mail bec

[Bug 232397] ctld does not depend on sysctl.conf being evaluated

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232397 Pete French changed: What|Removed |Added CC||p...@twisted.org.uk --- Comment #4 f

[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341 --- Comment #7 from VVD --- (In reply to Vladislav Shabanov from comment #6) Try to run ifconfig with each parameter: ifconfig igb0 -rxcsum ifconfig igb0 rxcsum ifconfig igb0 -rxcsum6 ifconfig igb0 rxcsum6 ifconfig igb0 -txcsum ifconfig igb

[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341 --- Comment #6 from Vladislav Shabanov --- (In reply to VVD from comment #5) Thanks. I applied all this -xxx options. Interestingly than the NIC hungs exactly after I executed this command line. Then I executed $ ifconfig igb0 -rxcsum -r

[Bug 254358] rc.conf.5: Document firewall_type "workstation"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254358 tobias.rehb...@web.de changed: What|Removed |Added Keywords||patch -- You are receiving

[Bug 254358] rc.conf.5: Document firewall_type "workstation"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254358 Bug ID: 254358 Summary: rc.conf.5: Document firewall_type "workstation" Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Sev

[Bug 254144] missing some directories and files in OptionalObsoleteFiles.inc

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254144 Dmitry Wagin changed: What|Removed |Added Summary|missing some directories in |missing some directories

[Bug 254144] missing some directories in OptionalObsoleteFiles.inc

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254144 Dmitry Wagin changed: What|Removed |Added Attachment #223101|0 |1 is obsolete|

[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341 --- Comment #5 from VVD --- (In reply to Vladislav Shabanov from comment #4) Sometimes something like this can help (workaround): ifconfig igb0 -rxcsum -rxcsum6 -txcsum -txcsum6 -tso -lro -vlanmtu -vlanhwtag -vlanhwfilter -vlanhwtso -- Yo