Re: Re: Re: bce0: Error mapping mbuf into TX chain!
On 8/10/06, David Christensen <[EMAIL PROTECTED]> wrote: 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 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! :-) cheers, scott ___ 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: Re: bce0: Error mapping mbuf into TX chain!
On 8/8/06, David (Controller AE) Christensen <[EMAIL PROTECTED]> wrote: > > Since BCE_MAX_SEGMENTS is too small I guess it will happen on highly > fragmented packets under heavy loads. To simulate the situation > you can use m_fragment(9) to fragment the frame in bce_tx_encap(). > With m_fragment(9), "ping -f -s 65507 x.x.x.x" may trigger it. > I didn't know about m_fragment before. I'll write a note to myself and look at how to add it to the debug path for a future driver revision. > Btw, I've never seen this small number of Tx DMA segments support( > BCE_MAX_SEGMENTS == 8) on GigE. Is this hardware limitation? > The real value for BCE_MAX_SEGMENTS should be 16, not 8. I chose 8 as a reasonable value to start with. If the number of fragments exceeds 16 then we would expect to see performance drop and it is probably faster to have the OS defragment the packet rather than try to perform so many DMAs. What I don't understand is why the driver stays locked up after it gets into this mode. I guess that's a separate issue from the low max segments which is triggering it in the first place? -scott ___ 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: Re: bce0: Error mapping mbuf into TX chain!
Hi Dave, On 8/7/06, David (Controller AE) Christensen <[EMAIL PROTECTED]> wrote: 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? Yes, that brought the interface to a halt very quickly! To answer what I was doing on the machine, it's running mysql with a fairly large database and most of the 8G of ram in the machine devoted to mysql. I'm running the amd64 on a Dell 1950 with Woodcrest series (5100) Xeon processors and BCM5708 NICs. cheers, scott > -----Original Message- > From: Scott Wilson [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 05, 2006 3:08 PM > To: [EMAIL PROTECTED] > Cc: Doug Ambrisko; David (Controller AE) Christensen; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; Eric Hodel > Subject: Re: Re: Re: bce0: Error mapping mbuf into TX chain! > > On 8/5/06, Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > > On Fri, Aug 04, 2006 at 03:52:40PM +0200, Scott Wilson wrote: > > > On 7/13/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote: > > > >David (Controller AE) Christensen writes: > > > >| Sorry, I've been out on vacation and just got back > into town. I'll MFC > > > >| the patch within the next day or two. > > > > > > > >I'll let you merge in the down/up fix that I put into -current. > > > > > > > >Doug A. > > > > > > Hi, I just had a bce interface lock up with the same problem: > > > > > > Aug 4 07:00:16 pe3 kernel: bce0: > /usr/src/sys/dev/bce/if_bce.c(4644): > > > Error mapping mbuf into TX chain! > > > Aug 4 07:00:47 pe3 last message repeated 368 times > > > > > > > > > running v 1.2.2.5 of if_bce.c from RELENG_6 which has the > > > defragmentation patch mentioned in this thread. Any > suggestions on > > > how I can help find a fix? > > > > > > scott > > > > Hmm... I can see several bus_dma(9) related bugs in bce(4). > > For architectures that have IOMMU hardware it may have corrupted DMA > > mapping and I'm pretty sure it wouldn't work on sparc64. > > When it has to handle many fragmented frame or has insufficient > > number of free Tx descriptors it would show unexpected results. > > Unfortunately I don't have hardwares supported by bce(4) and > > fixing requiries a working hardware. :-( > > > > I see ... I am running amd64 on some dell poweredge 1950 boxes. > They're xeon processors, but have chosen amd64 because they have 8gig > of ram each. > > Here are the relevant details on the interface > > bce0: mem > 0xf400-0xf5ff irq 16 at device 0.0 on pci9 > bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz > miibus0: on bce0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > > I could make a machine available remotely to someone if it would help. > > Any other advice on how I can help move this forward would be greatly > appreciated! > > thanks, > > scott > > ___ 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!
On 8/5/06, Pyun YongHyeon <[EMAIL PROTECTED]> wrote: On Fri, Aug 04, 2006 at 03:52:40PM +0200, Scott Wilson wrote: > On 7/13/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote: > >David (Controller AE) Christensen writes: > >| Sorry, I've been out on vacation and just got back into town. I'll MFC > >| the patch within the next day or two. > > > >I'll let you merge in the down/up fix that I put into -current. > > > >Doug A. > > Hi, I just had a bce interface lock up with the same problem: > > Aug 4 07:00:16 pe3 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(4644): > Error mapping mbuf into TX chain! > Aug 4 07:00:47 pe3 last message repeated 368 times > > > running v 1.2.2.5 of if_bce.c from RELENG_6 which has the > defragmentation patch mentioned in this thread. Any suggestions on > how I can help find a fix? > > scott Hmm... I can see several bus_dma(9) related bugs in bce(4). For architectures that have IOMMU hardware it may have corrupted DMA mapping and I'm pretty sure it wouldn't work on sparc64. When it has to handle many fragmented frame or has insufficient number of free Tx descriptors it would show unexpected results. Unfortunately I don't have hardwares supported by bce(4) and fixing requiries a working hardware. :-( I see ... I am running amd64 on some dell poweredge 1950 boxes. They're xeon processors, but have chosen amd64 because they have 8gig of ram each. Here are the relevant details on the interface bce0: mem 0xf400-0xf5ff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus0: on bce0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto I could make a machine available remotely to someone if it would help. Any other advice on how I can help move this forward would be greatly appreciated! thanks, scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: bce0: Error mapping mbuf into TX chain!
On 7/13/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote: David (Controller AE) Christensen writes: | Sorry, I've been out on vacation and just got back into town. I'll MFC | the patch within the next day or two. I'll let you merge in the down/up fix that I put into -current. Doug A. Hi, I just had a bce interface lock up with the same problem: Aug 4 07:00:16 pe3 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX chain! Aug 4 07:00:47 pe3 last message repeated 368 times running v 1.2.2.5 of if_bce.c from RELENG_6 which has the defragmentation patch mentioned in this thread. Any suggestions on how I can help find a fix? scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
