Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sun, May 12, 2019, 9:28 PM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > Eugene Grosbein wrote: > > > 11.05.2019 22:59, Julian H. Stacey wrote: > > > > > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > > > >> > > > I've posted a review to remove obsolete 10 and 10/100 Ethernet > drivers > > > as previous approved in FCP-101. > > > The following drivers are slated for > > > removal from FreeBSD-HEAD (to be FreeBSD-13): > > > > > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, > xe > > > >>> > > > >>> OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > >>> spare) that will never be able to upgrade. > > > >> > > > >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > > >> What kind of hardware do they have (CPU and memory-wise)? > > > > > > > > Thanks for question. I ran a quick check: > > > > cd /usr/src; > > > > # Apply my patches: > > > > # customise `pwd` > > > > # http://www.berklix.com/~jhs/bin/.csh/customise > > > > cd /sys/amd64/conf > > > > grep device [A-Z][A-Z][A-Z][A-Z].small | grep ed > > > > DUAL.small:device ed > > > > FILM.small:device ed > > > > KING.small:device ed > > > > LAPA.small:device ed > > > > LAPD.small:device ed > > > > LAPL.small:device ed > > > > LAPN.small:device ed > > > > LOFT.small:device ed > > > > MINI.small:device ed > > > > SCAN.small:device ed0 at isa? port 0x280 irq 15 iomem 0xd iosiz > 0x1 > > > > SLIM.small:device ed > > > > SNOW.small:device ed0 at isa? port 0x280 irq 5 iomem 0xc8000 > > > > WIND.small:device ed > > > > > > I've asked not for configuration files but for description of hardware. > > > ed(4) supports many different models. Some of them do 10Mbps only > > > but some are 100M-capable including PCI-connected. > > > > > > And it's interesting to know what is CPU and memory type/amount of > boxes. > > > > Info I had long pre saved, exported here: > > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/ > > Many boxes run newer releases than logs show, but eg dmesg shows memory > etc. > > It would help if you could run this from the hosts directory above and > post the output here, I doubt anyone besides me well bother looking > any further than this email at this data, but they well if you post > this output: > > find . -type f | grep /dmesg | xargs egrep 'CPU:|real memory|Ethernet' > > That should give us machine name by file path, CPU type, memory and > what ethernet cards are in it. > > I found one box, the second one I looked at, > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/logs/blak/dmesg0 > that clearly has enough CPU and memory to run 13: > CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) > real memory = 536858624 (511 MB) > ed0: at port 0x240-0x25f iomem 0xcc000-0xc > irq 5 pnpid EDI0119 on isa0 > ed0: [ITHREAD] > ed0: WARNING: using obsoleted if_watchdog interface > ed0: Ethernet address: 00:00:b4:36:a5:04 > > > Re Gary's: > > > 2) what versions of FBSD is Julian now running on his hardware? > > > 3) does he ever plan to upgrade this hardware to >= FBSD 13? > > > > Not many, if any of them; I should idealy find time to purge some, > > but I also have sundry newer PCs, & spare ed etc cards, so a pity to > loose ed. > > > > > > More generaly It won't be just me with ed. With 13 I can power up any > time, > > (+ other pcmcia & PCI & ISA cards in boxes) there's probably many more > globaly. > > > > But sys admins often don't have time to read developer lists like > > current@ & arch@. So developer considering zapping things, will > > not be seen by users it will hit later. > > > > First many will know is seeing in a RELNOTES "XYZ will be removed > > in release [0-9].[0-9]" No chance to answer an earlier "Are many > > still using XYZ, we're thinking of deleting it ?" > > I believe all of the proposed cards have been announcing > they are gone in FreeBSD 13 starting at FreeBSD 12. > > I am NOT clear if these gonein notices got backported to > 11, if not they should be ASAP as getting notice out to > the 11.3 users is important too. > > > If ed is the biggest legacy NIC, best be cautious ? > > I agree to some extent, but have no hard use evedence. > Last time I ran the reports from nycbug dmesg reports. Ed was rare starting in 7, and absent 9 and newer. That suggests it's once dominant position has decayed to almost nothing in the 25 years since it was king. I'd included this data at some point in the past, I thought. Warner > (BTW I also have 2 boxes running today's current, not just old Rels here.) > > > > Cheers, > > Julian > > -- > > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich > Aachen Kent > > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in > EU. > > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers > died. > > ___ > > freebsd-curr...@freebsd.org mailing list > >
Re: FCP-101: obsolete driver removal planned for 2019-05-18
> Eugene Grosbein wrote: > > 11.05.2019 22:59, Julian H. Stacey wrote: > > > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > > >> > > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > > as previous approved in FCP-101. > > The following drivers are slated for > > removal from FreeBSD-HEAD (to be FreeBSD-13): > > > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > >>> > > >>> OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > >>> spare) that will never be able to upgrade. > > >> > > >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > >> What kind of hardware do they have (CPU and memory-wise)? > > > > > > Thanks for question. I ran a quick check: > > > cd /usr/src; > > > # Apply my patches: > > > # customise `pwd` > > > # http://www.berklix.com/~jhs/bin/.csh/customise > > > cd /sys/amd64/conf > > > grep device [A-Z][A-Z][A-Z][A-Z].small | grep ed > > > DUAL.small:device ed > > > FILM.small:device ed > > > KING.small:device ed > > > LAPA.small:device ed > > > LAPD.small:device ed > > > LAPL.small:device ed > > > LAPN.small:device ed > > > LOFT.small:device ed > > > MINI.small:device ed > > > SCAN.small:device ed0 at isa? port 0x280 irq 15 iomem 0xd iosiz > > > 0x1 > > > SLIM.small:device ed > > > SNOW.small:device ed0 at isa? port 0x280 irq 5 iomem 0xc8000 > > > WIND.small:device ed > > > > I've asked not for configuration files but for description of hardware. > > ed(4) supports many different models. Some of them do 10Mbps only > > but some are 100M-capable including PCI-connected. > > > > And it's interesting to know what is CPU and memory type/amount of boxes. > > Info I had long pre saved, exported here: > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/ > Many boxes run newer releases than logs show, but eg dmesg shows memory etc. It would help if you could run this from the hosts directory above and post the output here, I doubt anyone besides me well bother looking any further than this email at this data, but they well if you post this output: find . -type f | grep /dmesg | xargs egrep 'CPU:|real memory|Ethernet' That should give us machine name by file path, CPU type, memory and what ethernet cards are in it. I found one box, the second one I looked at, http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/logs/blak/dmesg0 that clearly has enough CPU and memory to run 13: CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) real memory = 536858624 (511 MB) ed0: at port 0x240-0x25f iomem 0xcc000-0xc irq 5 pnpid EDI0119 on isa0 ed0: [ITHREAD] ed0: WARNING: using obsoleted if_watchdog interface ed0: Ethernet address: 00:00:b4:36:a5:04 > Re Gary's: > > 2) what versions of FBSD is Julian now running on his hardware? > > 3) does he ever plan to upgrade this hardware to >= FBSD 13? > > Not many, if any of them; I should idealy find time to purge some, > but I also have sundry newer PCs, & spare ed etc cards, so a pity to loose ed. > > > More generaly It won't be just me with ed. With 13 I can power up any time, > (+ other pcmcia & PCI & ISA cards in boxes) there's probably many more > globaly. > > But sys admins often don't have time to read developer lists like > current@ & arch@. So developer considering zapping things, will > not be seen by users it will hit later. > > First many will know is seeing in a RELNOTES "XYZ will be removed > in release [0-9].[0-9]" No chance to answer an earlier "Are many > still using XYZ, we're thinking of deleting it ?" I believe all of the proposed cards have been announcing they are gone in FreeBSD 13 starting at FreeBSD 12. I am NOT clear if these gonein notices got backported to 11, if not they should be ASAP as getting notice out to the 11.3 users is important too. > If ed is the biggest legacy NIC, best be cautious ? I agree to some extent, but have no hard use evedence. > (BTW I also have 2 boxes running today's current, not just old Rels here.) > > Cheers, > Julian > -- > Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent > http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. > Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. > ___ > freebsd-curr...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Rod Grimes rgri...@freebsd.org ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
Eugene Grosbein wrote: > 11.05.2019 22:59, Julian H. Stacey wrote: > > >> 11.05.2019 21:32, Julian H. Stacey wrote: > >> > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > as previous approved in FCP-101. > The following drivers are slated for > removal from FreeBSD-HEAD (to be FreeBSD-13): > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > >>> > >>> OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > >>> spare) that will never be able to upgrade. > >> > >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? > >> What kind of hardware do they have (CPU and memory-wise)? > > > > Thanks for question. I ran a quick check: > > cd /usr/src; > > # Apply my patches: > > # customise `pwd` > > # http://www.berklix.com/~jhs/bin/.csh/customise > > cd /sys/amd64/conf > > grep device [A-Z][A-Z][A-Z][A-Z].small | grep ed > > DUAL.small:device ed > > FILM.small:device ed > > KING.small:device ed > > LAPA.small:device ed > > LAPD.small:device ed > > LAPL.small:device ed > > LAPN.small:device ed > > LOFT.small:device ed > > MINI.small:device ed > > SCAN.small:device ed0 at isa? port 0x280 irq 15 iomem 0xd iosiz 0x1 > > SLIM.small:device ed > > SNOW.small:device ed0 at isa? port 0x280 irq 5 iomem 0xc8000 > > WIND.small:device ed > > I've asked not for configuration files but for description of hardware. > ed(4) supports many different models. Some of them do 10Mbps only > but some are 100M-capable including PCI-connected. > > And it's interesting to know what is CPU and memory type/amount of boxes. Info I had long pre saved, exported here: http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/hosts/ Many boxes run newer releases than logs show, but eg dmesg shows memory etc. Re Gary's: > 2) what versions of FBSD is Julian now running on his hardware? > 3) does he ever plan to upgrade this hardware to >= FBSD 13? Not many, if any of them; I should idealy find time to purge some, but I also have sundry newer PCs, & spare ed etc cards, so a pity to loose ed. More generaly It won't be just me with ed. With 13 I can power up any time, (+ other pcmcia & PCI & ISA cards in boxes) there's probably many more globaly. But sys admins often don't have time to read developer lists like current@ & arch@. So developer considering zapping things, will not be seen by users it will hit later. First many will know is seeing in a RELNOTES "XYZ will be removed in release [0-9].[0-9]" No chance to answer an earlier "Are many still using XYZ, we're thinking of deleting it ?" If ed is the biggest legacy NIC, best be cautious ? (BTW I also have 2 boxes running today's current, not just old Rels here.) Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem reports for n...@freebsd.org that need special attention
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 obsolete releases. Status |Bug Id | Description +---+--- In Progress |221146 | [ixgbe] Problem with second laggport In Progress |235700 | oce(4) driver causes fatal trap 12 on boot with e New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New |205592 | TCP processing in IPSec causes kernel panic New |213410 | [carp] service netif restart causes hang only whe Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open|200319 | Bridge+CARP crashes/freezes Open|202510 | [CARP] advertisements sourced from CARP IP cause Open|73 | igb(4): Kernel panic (fatal trap 12) due to netwo Open|227720 | Kernel panic in ppp server Open|233952 | jme NICs non functional after 11.2 to 12.0 upgrad Open|236888 | ppp daemon: Allow MTU to be overridden for PPPoE Open|236983 | bnxt(4) VLAN not operational unless explicit "ifc Open|237072 | netgraph(4): performance issue [on HardenedBSD]? Open|237391 | route get returns no result for network addresses 15 problems total for which you should take action. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sun, 2019-05-12 at 10:45 -0700, Rodney W. Grimes wrote: > > 12.05.2019 8:21, Warner Losh wrote: > > > > > >> I've posted a review to remove obsolete 10 and 10/100 > > > Ethernet drivers > > > >> as previous approved in FCP-101. > > > >> The following drivers are slated for > > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, > > > vx, wb, xe > > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show > > > box of > > > > spare) that will never be able to upgrade. > > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > > What kind of hardware do they have (CPU and memory-wise)? > > > > > > There are no 100M ed variants. There are some PC Card variants > > > that have 100M MII connections, but they are limited to about > > > 12Mbps due to bus limits. Even the PCI ones didn't have 100M mii > > > connections. > > > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 > > adapter. > > Not sure if ed(4) supports RTL8029AS. > > That is what I was hunting for, but I can not seem to > locate a data sheet on that. > > I also thought there was a 100mb version of the DP83905, > but can not seem to locate any data thier either. > > Given this lack of findable data I shall continue to support > the ed removal, unless Julian comes up with the needed criteria, > and with holding my own fact that I do have a pile of these > around, but they are not in use and are only retained for > testing and resurection of ancient things. > We should not lose track of the fact that the operative question here isn't "are you using an ed(4) device?", but rather "do you have systems containing an ed(4) device which are capable of running freebsd 13 and that you plan on updating to freebsd 13 or later?" Many of the systems that contained these old devices don't have enough ram to run a modern version of freebsd. If you can't update the system to 13, you don't need ongoing ed(4) support. And make no mistake, ongoing support IS the issue -- it costs manpower we don't have much of to maintain old device drivers. -- Ian ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
> 12.05.2019 8:21, Warner Losh wrote: > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet > > drivers > > >> as previous approved in FCP-101. > > >> The following drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > spare) that will never be able to upgrade. > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > What kind of hardware do they have (CPU and memory-wise)? > > > > There are no 100M ed variants. There are some PC Card variants that have > > 100M MII connections, but they are limited to about 12Mbps due to bus > > limits. Even the PCI ones didn't have 100M mii connections. > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. > Not sure if ed(4) supports RTL8029AS. That is what I was hunting for, but I can not seem to locate a data sheet on that. I also thought there was a 100mb version of the DP83905, but can not seem to locate any data thier either. Given this lack of findable data I shall continue to support the ed removal, unless Julian comes up with the needed criteria, and with holding my own fact that I do have a pile of these around, but they are not in use and are only retained for testing and resurection of ancient things. -- Rod Grimes rgri...@freebsd.org ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sun, May 12, 2019, 12:00 PM Eugene Grosbein wrote: > 12.05.2019 8:21, Warner Losh wrote: > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet > drivers > > >> as previous approved in FCP-101. > > >> The following drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, > xe > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > spare) that will never be able to upgrade. > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > What kind of hardware do they have (CPU and memory-wise)? > > > > There are no 100M ed variants. There are some PC Card variants that have > 100M MII connections, but they are limited to about 12Mbps due to bus > limits. Even the PCI ones didn't have 100M mii connections. > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. > Not sure if ed(4) supports RTL8029AS. > It does, but there is the same limitations. The card can't do DMA, so it's limited by inb/outb limitations. It also only has a 10Mbps transceiver built in. If people sold 100M attachments, it still won't do much more than 10Mbps. Warner > ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
13.05.2019 0:00, Eugene Grosbein wrote: > 12.05.2019 8:21, Warner Losh wrote: > >> >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers >> >> as previous approved in FCP-101. >> >> The following drivers are slated for >> >> removal from FreeBSD-HEAD (to be FreeBSD-13): >> >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe >> > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of >> > spare) that will never be able to upgrade. >> Do those boxes have 10M-only or 100Mbps variants of ed(4)? >> What kind of hardware do they have (CPU and memory-wise)? >> >> There are no 100M ed variants. There are some PC Card variants that have >> 100M MII connections, but they are limited to about 12Mbps due to bus >> limits. Even the PCI ones didn't have 100M mii connections. > > There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. > Not sure if ed(4) supports RTL8029AS. Sorry, my memory failed me. RTL8029AS was capable of 10Mbps full duplex (20Mbps in total) but had 10BaseT transceiver only. I wonder what is applicability of 10Mbps hardware these days. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
12.05.2019 8:21, Warner Losh wrote: > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > >> as previous approved in FCP-101. > >> The following drivers are slated for > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > spare) that will never be able to upgrade. > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > What kind of hardware do they have (CPU and memory-wise)? > > There are no 100M ed variants. There are some PC Card variants that have 100M > MII connections, but they are limited to about 12Mbps due to bus limits. Even > the PCI ones didn't have 100M mii connections. There was RTL8029AS "NE2000-compatible" 100M 32 bit PCI 2.1 adapter. Not sure if ed(4) supports RTL8029AS. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 128030] [ipsec] Enable IPSec in GENERIC kernel configuration
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=128030 Miroslav Lachman <000.f...@quip.cz> changed: What|Removed |Added CC||000.f...@quip.cz --- Comment #31 from Miroslav Lachman <000.f...@quip.cz> --- Was or will be ipsec related ports maintainers notified about this change / need of kldload? E.g. security/strongswan -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 237843] arp: Skips all name lookups if first fail with TRY_AGAIN
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237843
--- Comment #3 from p...@twisted.org.uk ---
Wasn't supposed to be a patch, as its not a real fix - its removing intended
functionality to let me debug what was going on, which is not a great way to
proceed, but for reference the diff looks like this:
--- arp.c 2019-05-12 10:20:57.920473000 +0100
+++ /usr/src/usr.sbin/arp/arp.c 2018-11-11 17:59:35.794752000 +
@@ -605,8 +605,11 @@
hp = 0;
if (hp)
host = hp->h_name;
- else
+ else {
host = "?";
+ if (h_errno == TRY_AGAIN)
+ nflag = 1;
+ }
xo_emit("{:hostname/%s} ({:ip-address/%s}) at ", host,
inet_ntoa(addr->sin_addr));
if (sdl->sdl_alen) {
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 237843] arp: Skips all name lookups if first fail with TRY_AGAIN
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237843
--- Comment #4 from p...@twisted.org.uk ---
Gah, thats backwards of course! here it is with the arguments the right way
round :)
--- /usr/src/usr.sbin/arp/arp.c 2018-11-11 17:59:35.794752000 +
+++ arp.c 2019-05-12 10:20:57.920473000 +0100
@@ -605,11 +605,8 @@
hp = 0;
if (hp)
host = hp->h_name;
- else {
+ else
host = "?";
- if (h_errno == TRY_AGAIN)
- nflag = 1;
- }
xo_emit("{:hostname/%s} ({:ip-address/%s}) at ", host,
inet_ntoa(addr->sin_addr));
if (sdl->sdl_alen) {
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Sat, 11 May 2019 20:21:46 -0500 Warner Losh wrote: > On Sat, May 11, 2019, 12:52 PM Eugene Grosbein wrote: > > > 11.05.2019 21:32, Julian H. Stacey wrote: > > > > >> I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > > >> as previous approved in FCP-101. > > >> The following drivers are slated for > > >> removal from FreeBSD-HEAD (to be FreeBSD-13): > > >> > > >> ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > > > > > OMG ! ed ! That EOL's loads of PC boxes I have (& a show box of > > > spare) that will never be able to upgrade. > > > > Do those boxes have 10M-only or 100Mbps variants of ed(4)? > > What kind of hardware do they have (CPU and memory-wise)? > > > More relevant questions might be 1) will these drivers only be removed from FBSD >= 13? 2) what versions of FBSD is Julian now running on his hardware? 3) does he ever plan to upgrade this hardware to >= FBSD 13? I know Julian and he has an amazing collection of old hardware. I suspect that most of it will not even be able to run FBSD 13. > > There are no 100M ed variants. There are some PC Card variants that have > 100M MII connections, but they are limited to about 12Mbps due to bus > limits. Even the PCI ones didn't have 100M mii connections. > -- Gary Jennejohn (gj@) ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 128030] [ipsec] Enable IPSec in GENERIC kernel configuration
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=128030 --- Comment #30 from Kubilay Kocak --- Author: gallatin Date: Thu May 9 22:38:15 2019 New Revision: 347410 URL: https://svnweb.freebsd.org/changeset/base/347410 Log: Remove IPSEC from GENERIC due to performance issues Having IPSEC compiled into the kernel imposes a non-trivial performance penalty on multi-threaded workloads due to IPSEC refcounting. In my benchmarks of multi-threaded UDP transmit (connected sockets), I've seen a roughly 20% performance penalty when the IPSEC option is included in the kernel (16.8Mpps vs 13.8Mpps with 32 senders on a 14 core / 28 HTT Xeon 2697v3)). This is largely due to key_addref() incrementing and decrementing an atomic reference count on the default policy. This cause all CPUs to stall on the same cacheline, as it bounces between different CPUs. Given that relatively few users use ipsec, and that it can be loaded as a module, it seems reasonable to ask those users to load the ipsec module so as to avoid imposing this penalty on the GENERIC kernel. Its my hope that this will make FreeBSD look better in "out of the box" benchmark comparisons with other operating systems. Many thanks to ae for fixing auto-loading of ipsec.ko when ifconfig tries to configure ipsec, and to cy for volunteering to ensure the the racoon ports will load the ipsec.ko module Reviewed by: cem, cy, delphij, gnn, jhb, jpaetzel Differential Revision:https://reviews.freebsd.org/D20163 Modified: head/UPDATING head/sys/amd64/conf/GENERIC head/sys/arm/conf/std.armv6 head/sys/arm/conf/std.armv7 head/sys/arm64/conf/GENERIC head/sys/i386/conf/GENERIC head/sys/powerpc/conf/GENERIC head/sys/powerpc/conf/GENERIC64 head/sys/riscv/conf/GENERIC head/sys/sparc64/conf/GENERIC -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
