Re: kern/112710: if_re driver detects incorrect b243a405a405 MAC address on SMC9452TX-1 pci gigabit cards
Synopsis: if_re driver detects incorrect b243a405a405 MAC address on SMC9452TX-1 pci gigabit cards Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Wed May 16 14:17:56 UTC 2007 Responsible-Changed-Why: if_re is a networking thing, reassign to the network group. http://www.freebsd.org/cgi/query-pr.cgi?pr=112710 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/112654: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000
Synopsis: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Wed May 16 14:20:04 UTC 2007 Responsible-Changed-Why: This is something networking related, reassign to networking. http://www.freebsd.org/cgi/query-pr.cgi?pr=112654 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/112670: [if_tap] stat /dev/tapN leads to panic for N >= 2G
Synopsis: [if_tap] stat /dev/tapN leads to panic for N >= 2G State-Changed-From-To: open->feedback State-Changed-By: remko State-Changed-When: Wed May 16 16:36:49 UTC 2007 State-Changed-Why: Hello, it is being mentioned that -STABLE has the required fixed, can you please upgrade your station to -STABLE and report whether that indeed solved the problem. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=112670 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EM and TSO
I introduced a change yesterday that limited TSO to PCI Express adapters, I did this more for avoidance rather than a bug fix, and I'm not 100% sure its the right thing, so I thought I would poll everyone, do you have a PCI-X adapter and are using TSO without problems and wish to keep the support in? If no one is then I'll just leave it as is. Jack ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
Jack Vogel wrote: I introduced a change yesterday that limited TSO to PCI Express adapters, I did this more for avoidance rather than a bug fix, and I'm not 100% sure its the right thing, so I thought I would poll everyone, do you have a PCI-X adapter and are using TSO without problems and wish to keep the support in? I'm using the dual-port PCI-X adapter and would like to keep using TSO on it. There are a lot of those adapters out there in servers. TSO is scheduled to be MFC'd really soon now and not having it work with em(4) on PCI-X would be quite limiting. -- Andre ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
On 5/16/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: Jack Vogel wrote: > I introduced a change yesterday that limited TSO to PCI Express > adapters, I did this more for avoidance rather than a bug fix, and > I'm not 100% sure its the right thing, so I thought I would poll > everyone, do you have a PCI-X adapter and are using TSO without > problems and wish to keep the support in? I'm using the dual-port PCI-X adapter and would like to keep using TSO on it. There are a lot of those adapters out there in servers. TSO is scheduled to be MFC'd really soon now and not having it work with em(4) on PCI-X would be quite limiting. OK, I'll put it back, you also answered a question I had, namely the MFC of TSO :) I was hoping that got into 6.3. I have another bug I'm working on, will be a delta today or tomorrow and I'll put it back to what it was. Jack ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
Jack Vogel wrote: I introduced a change yesterday that limited TSO to PCI Express adapters, I did this more for avoidance rather than a bug fix, and I'm not 100% sure its the right thing, so I thought I would poll everyone, do you have a PCI-X adapter and are using TSO without problems and wish to keep the support in? If no one is then I'll just leave it as is. Jack Remember to CC the lists this time. I have a number of systems with built in em adapters (on the motherboard) is there any easy way to find out what type of bus these are connected to? Tom ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
On 5/16/07, Thomas Hurst <[EMAIL PROTECTED]> wrote: * Jack Vogel ([EMAIL PROTECTED]) wrote: > I introduced a change yesterday that limited TSO to PCI Express > adapters, I did this more for avoidance rather than a bug fix, and > I'm not 100% sure its the right thing, so I thought I would poll > everyone, do you have a PCI-X adapter and are using TSO without > problems and wish to keep the support in? > > If no one is then I'll just leave it as is. We put CURRENT on one of our Sun X4200's for some MySQL tests a few days ago and haven't noticed any problems, though it's only handled a few million packets so far. Does this change remove support or just disable it by default? It removed it, but Andre and my own guilty conscience has convinced me that I should change it back, once I get an MSI/X bug that was discovered with the code solved there will be another delta that will reenable it for PCI-X again. Jack ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
* Jack Vogel ([EMAIL PROTECTED]) wrote: > I introduced a change yesterday that limited TSO to PCI Express > adapters, I did this more for avoidance rather than a bug fix, and > I'm not 100% sure its the right thing, so I thought I would poll > everyone, do you have a PCI-X adapter and are using TSO without > problems and wish to keep the support in? > > If no one is then I'll just leave it as is. We put CURRENT on one of our Sun X4200's for some MySQL tests a few days ago and haven't noticed any problems, though it's only handled a few million packets so far. Does this change remove support or just disable it by default? -- Thomas 'Freaky' Hurst http://hur.st/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/112654: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000
The following reply was made to PR kern/112654; it has been noted by GNATS. From: Marius Strobl <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: kern/112654: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000 Date: Wed, 16 May 2007 19:59:01 +0200 I think this was fixed as part of src/sys/pci/if_pcn.c rev. 1.81/1.69.2.7 and src/sys/dev/mii/nsphy.c rev. 1.26/1.23.2.3. Could you please give a current FreeBSD-CURRENT or -STABLE a try? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
Jack Vogel wrote: On 5/16/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: Jack Vogel wrote: > I introduced a change yesterday that limited TSO to PCI Express > adapters, I did this more for avoidance rather than a bug fix, and > I'm not 100% sure its the right thing, so I thought I would poll > everyone, do you have a PCI-X adapter and are using TSO without > problems and wish to keep the support in? I'm using the dual-port PCI-X adapter and would like to keep using TSO on it. There are a lot of those adapters out there in servers. TSO is scheduled to be MFC'd really soon now and not having it work with em(4) on PCI-X would be quite limiting. OK, I'll put it back, you also answered a question I had, namely the MFC of TSO :) I was hoping that got into 6.3. I have another bug I'm working on, will be a delta today or tomorrow and I'll put it back to what it was. Jack ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" give a sysctl to change the option. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
You mean other than net.inet.tcp.tso that is there now? On 5/16/07, Julian Elischer <[EMAIL PROTECTED]> wrote: Jack Vogel wrote: > On 5/16/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: >> Jack Vogel wrote: >> > I introduced a change yesterday that limited TSO to PCI Express >> > adapters, I did this more for avoidance rather than a bug fix, and >> > I'm not 100% sure its the right thing, so I thought I would poll >> > everyone, do you have a PCI-X adapter and are using TSO without >> > problems and wish to keep the support in? >> >> I'm using the dual-port PCI-X adapter and would like to keep >> using TSO on it. There are a lot of those adapters out there >> in servers. TSO is scheduled to be MFC'd really soon now and >> not having it work with em(4) on PCI-X would be quite limiting. > > OK, I'll put it back, you also answered a question I had, namely > the MFC of TSO :) I was hoping that got into 6.3. > > I have another bug I'm working on, will be a delta today or tomorrow > and I'll put it back to what it was. > > Jack > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" give a sysctl to change the option. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/112670: [if_tap] stat /dev/tapN leads to panic for N >= 2G
On Wed, May 16, 2007 at 04:37:15PM +, Remko Lodder wrote: > Hello, it is being mentioned that -STABLE has the required fixed, can you > please > upgrade your station to -STABLE and report whether that indeed solved the > problem. > Thanks. Kernel 6.2 STABLE 200705 seems ok. Ludovico -- <[EMAIL PROTECTED]>#acheronte (irc.freenode.net) ICQ: 64483080 GPG ID: 07F89BB8 Jabber: [EMAIL PROTECTED] Yahoo: gardenghelle -- This is signature nr. 3089 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
Jack Vogel wrote: You mean other than net.inet.tcp.tso that is there now? I don't think another sysctl is necessary for this. -- Andre ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
Jack Vogel wrote: > I introduced a change yesterday that limited TSO to PCI Express > adapters, I did this more for avoidance rather than a bug fix, and > I'm not 100% sure its the right thing, so I thought I would poll > everyone, do you have a PCI-X adapter and are using TSO without > problems and wish to keep the support in? > > If no one is then I'll just leave it as is. It might be better to enable it by default on pci-e adapters and require manual enable on other adapters that are capable but may not function correctly. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/112670: [if_tap] stat /dev/tapN leads to panic for N >= 2G
The following reply was made to PR kern/112670; it has been noted by GNATS. From: Ariff Abdullah <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: kern/112670: [if_tap] stat /dev/tapN leads to panic for N >= 2G Date: Thu, 17 May 2007 05:33:48 +0800 This is a multi-part message in MIME format. --Multipart=_Thu__17_May_2007_05_33_48_+0800_IlHONeq=l+xq7q9C Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Grr... this was meant for kern/112670, not 112671. Sorry. Well, I'm not really sure if this is all about signess or simply because dev_stdclone() itself fail to do correct checking on unit > 0xff (it should be CLONE_UNITMASK which is 0xf, no?), obviously an overflow against clone_create(). It could be argued that the caller would later strip and truncate it, but there are few other drivers (notably snp(4)) which innocently proceed without any tinkering. Anyway, try this patch. It should help other dev_stdclone() users too. -- Ariff Abdullah FreeBSD ... Recording in stereo is obviously too advanced and confusing for us idiot * users :P --Multipart=_Thu__17_May_2007_05_33_48_+0800_IlHONeq=l+xq7q9C Content-Type: text/x-diff; name="kern_conf.c.diff" Content-Disposition: attachment; filename="kern_conf.c.diff" Content-Transfer-Encoding: 7bit Index: src/sys/kern/kern_conf.c === RCS file: /home/ncvs/src/sys/kern/kern_conf.c,v retrieving revision 1.201 diff -u -r1.201 kern_conf.c --- src/sys/kern/kern_conf.c 2 Feb 2007 22:27:45 - 1.201 +++ src/sys/kern/kern_conf.c 16 May 2007 20:05:51 - @@ -763,7 +763,7 @@ u *= 10; u += name[i++] - '0'; } - if (u > 0xff) + if (u > CLONE_UNITMASK) return (0); *unit = u; if (namep) --Multipart=_Thu__17_May_2007_05_33_48_+0800_IlHONeq=l+xq7q9C-- ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/112722: IP v4 udp fragmented packet reject
Synopsis: IP v4 udp fragmented packet reject Responsible-Changed-From-To: freebsd-amd64->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed May 16 22:12:30 UTC 2007 Responsible-Changed-Why: This does not sound amd64-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=112722 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
Jack Vogel wrote: > You mean other than net.inet.tcp.tso that is there now? > > On 5/16/07, Julian Elischer <[EMAIL PROTECTED]> wrote: >> Jack Vogel wrote: >> > On 5/16/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: >> >> Jack Vogel wrote: >> >> > I introduced a change yesterday that limited TSO to PCI Express >> >> > adapters, I did this more for avoidance rather than a bug fix, and >> >> > I'm not 100% sure its the right thing, so I thought I would poll >> >> > everyone, do you have a PCI-X adapter and are using TSO without >> >> > problems and wish to keep the support in? >> >> >> >> I'm using the dual-port PCI-X adapter and would like to keep >> >> using TSO on it. There are a lot of those adapters out there >> >> in servers. TSO is scheduled to be MFC'd really soon now and >> >> not having it work with em(4) on PCI-X would be quite limiting. >> > >> > OK, I'll put it back, you also answered a question I had, namely >> > the MFC of TSO :) I was hoping that got into 6.3. >> > >> > I have another bug I'm working on, will be a delta today or tomorrow >> > and I'll put it back to what it was. >> > >> > Jack >> > ___ >> > freebsd-net@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >> > To unsubscribe, send any mail to "[EMAIL PROTECTED]" >> >> give a sysctl to change the option. ifconfig can be used to ena/dis tso. As I said before just give all the devices capable of tso the capability but only enable it by default on those devices you really know work (e.g. pci-e cards). On other devices users that want to turn it on can do so with ifconfig. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EM and TSO
On 5/16/07, Sam Leffler <[EMAIL PROTECTED]> wrote: Jack Vogel wrote: > You mean other than net.inet.tcp.tso that is there now? > > On 5/16/07, Julian Elischer <[EMAIL PROTECTED]> wrote: >> Jack Vogel wrote: >> > On 5/16/07, Andre Oppermann <[EMAIL PROTECTED]> wrote: >> >> Jack Vogel wrote: >> >> > I introduced a change yesterday that limited TSO to PCI Express >> >> > adapters, I did this more for avoidance rather than a bug fix, and >> >> > I'm not 100% sure its the right thing, so I thought I would poll >> >> > everyone, do you have a PCI-X adapter and are using TSO without >> >> > problems and wish to keep the support in? >> >> >> >> I'm using the dual-port PCI-X adapter and would like to keep >> >> using TSO on it. There are a lot of those adapters out there >> >> in servers. TSO is scheduled to be MFC'd really soon now and >> >> not having it work with em(4) on PCI-X would be quite limiting. >> > >> > OK, I'll put it back, you also answered a question I had, namely >> > the MFC of TSO :) I was hoping that got into 6.3. >> > >> > I have another bug I'm working on, will be a delta today or tomorrow >> > and I'll put it back to what it was. >> > >> > Jack >> > ___ >> > freebsd-net@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >> > To unsubscribe, send any mail to "[EMAIL PROTECTED]" >> >> give a sysctl to change the option. ifconfig can be used to ena/dis tso. As I said before just give all the devices capable of tso the capability but only enable it by default on those devices you really know work (e.g. pci-e cards). On other devices users that want to turn it on can do so with ifconfig. I like this, good compromise. Thanks Sam :) Should be coming into tree shortly. Jack ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problem with my routing I believe
Hello, I’m in the process of trying to setup a freebsd box to act as a gateway. This box contains 3 network cards. Here is how it is divided. 1) Network card 1 goes to the modem for internet access. 2) Network card 2 has a network class of 192.168.1.0 and plugs in directory to another computer 192.168.1.5 (both gateway network card and other computer have static ips) 3) Network card 3 has a network class of 192.168.2.0 and has dhcp running on it, giving out dynamic ips to several other computers (not including the one discussed above) All netmasks are 255.255.255.0 As you can see, I’m trying to run two networks and give them both access to the internet. Any of the computers which are running under dhcp can access anything just fine. Computer under the class of 192.168.1.0 cannot ping anyone. On the gateway, I can ping the computer with the static IP, but it is VERY slow. Anyone ever encountered this before? Any possible solutions? If there is a more appropriate mailing list for this type of question, please let me know. Thanks! Tom Cruickshank Internal Virus Database is out-of-date. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 269.6.1/778 - Release Date: 27/04/2007 1:39 PM ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Port of the new em(4) to RELENG_6 and some problems with 82540EM
Jack, good day. I happened to make a quick and dirty patch for your latest (for the 16.05.2007) em(4) driver from 7-CURRENT. I had seen that you mentioned TSO and 6.3, so I assume that you're going to merge the driver to the RELENG_6 someday, so maybe my effort may be helpful. To my problems. I have the '82540EM Gigabit Ethernet Controller' branded card (PWLA8390MT) and I am currently expiriencing troubles with the Gigabit switch (D-Link DGS-1008, the cheap one). Plugged into that switch I have - broken packets and SSH messages 'Disconnecting: Corrupted MAC on input.' when checksumming is turned on and gigabit speed, - abyssmal rates for the HTTP downloads (about 10Mbit/sec) when checksums are turned off and the speed is gigabit again, - having switched the media on the adapter to the 100BaseTX full-duplex, but still using the same switch the speed drops to 200Kbit/sec, - using another D-Link switch (sorry, have no other brand in hand) the above situation is completely reproducible. - working in the half-duplex mode (for 10BaseT/UTP and 100BaseTX) I have no problems to reach the 90% of the theoretical bandwidth of the link via HTTP either with checksums enabled or disabled. So, the full-duplex mode is not usable to me now. If someone can help in this situation, I am all ears. I thought that new driver may introduce some fixes, but it isn't: the situation is the same. I will continue my investigations, but just in case you're interested in my port, it is available from http://codelabs.ru/patches/fbsd/em-6.5.0-initial.patch.bz2 RELENG_6 and 7-CURRENT sources were CVSupped yesterday, 16 May 2007. TSO-related stuff is completely disabled for the RELENG_6. My limited testing of the driver revealed no problems yet, but if they will arise I will report them. -- Eygene ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
