RE: HEADS UP: Plan to MFC new em driver
> I have a version of code ready to MFC, the big difference with CURRENT > is that TSO is #ifdef'd off until Andre is able to get that back. Is something broken with TSO? I just added TSO support to bce on CURRENT and was planning on MFC'ing to RELENG_6 within the next week. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: bge problems under 7.2-PRERELEASE
> > > Then update if_bge.c to rev > > > 1.198.2.14 and check whether things still work, > > > > this causes the problem to resurface. > > > > David, > > this is the second report that using MSI with a BCM5754/ > chip=0x167a14e4 results in no interrupts, is there any errata > about this? Nope, no errata for MSI on the 5754, nor can I recall any MSI problems on any of the PCIe based devices. Do the systems share a common root complex that might be the source of the issue? Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: bge problems under 7.2-PRERELEASE
> > > this is the second report that using MSI with a BCM5754/ > > > chip=0x167a14e4 results in no interrupts, is there any > errata about > > > this? > > > > Nope, no errata for MSI on the 5754, nor can I recall any > MSI problems > > on any of the PCIe based devices. Do the systems share a > common root > > complex that might be the source of the issue? > > > > This one useses a: > no...@pci0:0:0:0: class=0x05 card=0x02f010de > chip=0x02f010de rev=0xa2 hdr=0x00 > vendor = 'Nvidia Corp' > device = 'C51 Host Bridge' > class = memory > subclass = RAM > > At least Linux doesn't seem to avoid using MSI with these. > I didn't get any further regarding the other report so far. Are there any other errors reported by the 5754 such as a PCIe completion timeout in the Advanced Error Uncorrectable Status Register? I recall an issue with another Nvidia chipset and the 5754 where the system BIOS incorrectly configured the Hypertransport unitID field to a value of 0x20 which would prevent our diagnostics from running. PCI configuration and memory-mapped I/O worked correctly but DMA operations such as sending RX'd frames would fail. MSI might fall into this latter category and could be causing this error. The important thing would be to check for a Completion Timeout in the 5754. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: mini-HEADSUP bce owners: please test
> > David and I have committed some fixes to 7-STABLE tree, and I think > > all important bce(4) fixes has been merged now. If you have bce(4) > > interfaces PLEASE help us to test them, the simplest way of > doing this > > is to sync your code with RELENG_7 and rebuild kernel. [1] > > I won't have timer to try this until friday at the earliest, > but one question... is this likely to fix my infamous > lagg/lacp issue ? I notice it isn't in the list of known > issues. I will test anyway, but if you happen to be in that > bit of code *does best winning smile* :-) That should be the packet length fix at line 5973 of if_bce.c. I did not test the teaming fix myself but another user provided a similar packet length fix which he claimed did fix the issue so I'm hopeful that this should work for you too. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: mini-HEADSUP bce owners: please test
> Well, I found time to test this today after all - and it does > actually fix the issue - my bce devices now work properly > with lagg and lacp. Thanks for the confirmation. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Re: Re: bce0: Error mapping mbuf into TX chain!
Scott, > > What are you doing when this problem occurs? Is it something > I can easily duplicate here? When I tested the fix on > -CURRENT I used the following command suggested by Doug to > bring out the failure quickly: > > ssh "dd if=/dev/zero bs=1" > /dev/null > > Does this same command fail for you too? > I updated my RELENG_6 system to the tip and tried the same ssh command which you mentioned also failed on your system. I couldn't duplicate the problem at all. Are you sure you are actually using the new code? My system is reporting a different driver version than yours (mine = 0.9.6, yours = 0.9.5): bce0: mem 0xdc00-0xddff irq 16 at device 0.0 on pci2 bce0: ASIC ID 0x57081020; Revision (B2); PCI-X 64-bit 133MHz bce0: Ethernet address: 00:10:18:15:f6:96 Are you still having a problem? Can you change the version number in if_bce.c (bce_driver_version) and make sure the right driver is loading? Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Re: Re: bce0: Error mapping mbuf into TX chain!
> > Are you still having a problem? Can you change the version > number in > > if_bce.c (bce_driver_version) and make sure the right > driver is loading? > > > > Dave > > Hi Dave, > > Well spotted, my appologies for that. I was indedd running a slightly > older version of the driver. I may have mixed up my kernel build when > experimenting with sharing the same build tree over several machines. > > The driver seems to work fine now, that test no longer crashes it. I > also did some iperf tests between two machines with these cards ( the > other running linux) and I was getting ~950 MBit /sec between them! > > Thanks for your help! I'll keep beating on these machines for a few > days to come, but will be so glad to get them into productions, > they're so fast! :-) > Glad to hear things are working now. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: bce issues still outstanding
> > I've copied many of the people who I've been working with directly on > this issue. > > Can anyone provide a status update on these problems? > Discussion seems > to have stopped since Oct 5. > > Any new patches to test? > I'm sorry but I'm absolutely swamped with my day job 6.5 days a week and it's likely to continue for a few more weeks. Any questions about register settings or basic controller architecture that I can help out with quickly I'll be happy to respond to, but beyond that I'm not able to devote any resources into debugging this until my current work project has concluded. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: bce issues still outstanding
> Bill Moran wrote: > > I've copied many of the people who I've been working with > directly on > > this issue. > > > > Can anyone provide a status update on these problems? > Discussion seems > > to have stopped since Oct 5. > > > > Any new patches to test? > > > > I'm actively working on fixing the driver right now. > Thanks for the help Scott, is there anything I can do help with the process? Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Dell 1955 Blade - Broadcom NIC not detected (BCM5708S)
> > > >> Oops, you're right. I've been accidentally ignoring > this anyways, I'll > > > >> take care of it. Thanks! > > > >> > > > >> Scott > > > >> > > > > > > > >Thanks the kernel now recognizes the network interface. > > > > > > > >But it fails to "attach" the driver to the interface > and gives the > > > >following error. > > > >"bce0 if_bce.c(531) SerDes controllers are not supported!" > > > > > > > >What now is there anything else I can try? > > > > > > > >Regards > > > >Conrad > > > > > > > > > > In if_bce.c I found the following comment "/* DRC - > ToDo: Add SerDes > > > support. */". > > > > > > Looks like the SerDes code for the BCE driver still > needs to be developed :( > > > > > > If someone could finish the SerDes code for the driver, > I will spend > > > as much time as needed to test each code change that is > attempted to > > > get the SerDes stuff working :) > > > > > > If needs be I will hook a console up to the system to make it > > > accessible over the internet. > > > > > > > Because I don't the hardware and datasheet for the chip I can't make > > any further changes for you. Sorry. But you can ask the > driver author > > for a plan for SERDES transceiver support. CCed to David > Christensen, > > the author of the driver. > > > > I might try to take a look at this. I wonder if the Linux driver > already has support. > > Scott > Yes, the Linux bnx2 driver does support SerDes. I don't have the bandwidth to tackle this feature until after the first of the year, though a few other people have also considered looking into adding the support. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Dell 1955 Blade - Broadcom NIC not detected (BCM5708S)
> Hello Dave ! > > >Wed Nov 1 18:54:19 UTC 2006 > > > >Yes, the Linux bnx2 driver does support SerDes. I don't have the > >bandwidth to tackle this feature until after the first of the year, > >though a few other people have also considered looking into adding > >the support. > > > Any news or status report regarding support for this new > network interface > in FreeBSD ? I've copied Doug White who is working to add SerDes support to bce. Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
