Date: Mon, 7 Aug 2006 13:48:09 -0700 From: "David (Controller AE) Christensen" <davidch@broadcom.com> To: "Scott Wilson" <scott.wilson@gmail.com>, pyunyh@gmail.com Cc: stable@freebsd.org, davidch@freebsd.org, Eric Hodel <drbrain@segment7.net> Subject: RE: Re: Re: bce0: Error mapping mbuf into TX chain! Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD90301AB707F@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <abf642980608051507k49a5a025s7a05aaab8e7efe5e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <bad machine> "dd if=3D/dev/zero bs=3D1" > /dev/null Does this same command fail for you too? Dave=20 > -----Original Message----- > From: Scott Wilson [mailto:scott.wilson@gmail.com]=20 > Sent: Saturday, August 05, 2006 3:08 PM > To: pyunyh@gmail.com > Cc: Doug Ambrisko; David (Controller AE) Christensen;=20 > stable@freebsd.org; davidch@freebsd.org; Eric Hodel > Subject: Re: Re: Re: bce0: Error mapping mbuf into TX chain! >=20 > On 8/5/06, Pyun YongHyeon <pyunyh@gmail.com> wrote: > > On Fri, Aug 04, 2006 at 03:52:40PM +0200, Scott Wilson wrote: > > > On 7/13/06, Doug Ambrisko <ambrisko@ambrisko.com> wrote: > > > >David (Controller AE) Christensen writes: > > > >| Sorry, I've been out on vacation and just got back=20 > 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:=20 > /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=20 > 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. :-( > > >=20 > 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. >=20 > Here are the relevant details on the interface.... >=20 > bce0: <Broadcom NetXtreme II BCM5708 1000Base-T (B1), v0.9.5> mem > 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 > bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz > miibus0: <MII bus> on bce0 > brgphy0: <BCM5708C 10/100/1000baseTX PHY> on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto >=20 > I could make a machine available remotely to someone if it would help. >=20 > Any other advice on how I can help move this forward would be greatly > appreciated! >=20 > thanks, >=20 > scott >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?09BFF2FA5EAB4A45B6655E151BBDD90301AB707F>