Date: Tue, 1 Jun 1999 08:58:30 +0200 From: Alexander Maret <maret@axis.de> To: 'Bill Paul' <wpaul@skynet.ctr.columbia.edu> Cc: "'hackers@freebsd.org'" <hackers@freebsd.org> Subject: RE: xl driver for 3Com Message-ID: <91DA20EC3C3DD211833400A0245A4EA9BA0E4F@erlangen01.axis.de>
next in thread | raw e-mail | index | archive | help
Hi, > Well maybe FreeBSD is transmitting packets much faster than Linux. :) > You still haven't actually measured the transfer speed, so there's > no way for us to know. Well, I'll do and report the results to you. > Grrr. I'm sorry, but I really don't think you're putting the pieces > together correctly. Setting the NT machine to full duplex should have > absolutely no effect on the FreeBSD host. It will completely screw up > performance since the LoseNT host will then no longer be set to match > the hub, but that's another problem. I strongly suspect that you're > not making the proper observations when your problem manifests and > just leaping to the conclusion that setting the LoseNT host to full > duplex crashes the FreeBSD host. I just tell you what i experienced. > I don't think that's true. Why are you ignoring problems. On the one hand you want people to use your driver and complain if they switch to other cards and on the other hand you comment their problems with: That's not true. I don't think that so many collisions are normal! I think there is a problem, because at work we nearly only use 3COM 100 Mbit cards and don't have much collisions. Even under high load! Looking at the fact that at work not only two computers are connected to one hub but many, it would be more likely if we had many collisions. The only difference is that we only use NT Server/Workstation machines. Well I know you don't like what I wrote in my last paragraph and I know I will again get a very aggressive answer and I think at the end I will someday switch to other cards. Like many people. I think that your aggressive way to answer questions is another problem. Why do you think you don't get many bug reports or people switching to other hardware? > If both > machines are sitting idle (not transmitting any data) and you just > suddenly set the LoseNT host to full duplex, the FreeBSD machine isn't > going to just say "Hey! The LoseNT host changed modes! I better crash > now!" There must be more to it than that, but you're not going into > any detail. I don't know what's going on in the background. > Remember when I said I wanted *detailed* problem reports? Probably my english is too bad because I think saying "After switching my NT machine to FullDuplex my FreeBSD server resets immidiately" is a detailed bug report. Or should I say it like this: "I switched my NT machine to FullDuplex and in the same second my FreeBSD Server shows a black screen and then I see the bios-output of my graphic card. After that I see the normal BIOS output and then the computer reboots my FreeBSD." > This is why. How do we know there isn't some really explicit panic > message on the console that's screaming: "I crashed because of the > following reason: <foo>?" Maybe there's a message like that there, but > we'll never know unless you tell us! I would have told you any error messages. I think everybody would. > And you still haven't explained what you meant about the LoseNT > machine crashing before. As I said in an earlier mail: If there are too many collisions my NT server crashes. Sometimes it doesn't crash but I can't send any data over the net either. I think it has something to do with the TCP/IP protocol because I then can't ping the NT machine nor the FreeBSD server. I have to reboot NT and everything works fine again. I can easily reproduce this error. Even with another NT machine which shows the same problem. If I don't transfer much data on the net, like reading html-pages from my FreeBSD server, or listening to an mp3 file (via samba), I don't get any collisions and the NT machine doesn't crash. Well this bug report is probably not detailed enough for you, but that's what i experience and I just tell you what i see. If you tell me what EXACTLY i shall look for, I'll do. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91DA20EC3C3DD211833400A0245A4EA9BA0E4F>