Re: Fixes for kern/40018 -- any chance of getting these pulled into the -current and 5.x trees?

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        Hello.  Is this something you can reproduce easily?  I wonder if the
ethernet chip is just hanging, and the rest of the machine is fine?
Which bits are you turning on?  just:
ip4csum, tcp4csum and udp4csum?
        If the two machines have different revisions of the chip, that
could explain why one works and the other doesn't.  I suspect that you
might be tripping over a chip bug, rather than a driver bug.
-Brian

On Oct 30, 12:51am, Martin Husemann wrote:
} Subject: Re: Fixes for kern/40018 -- any chance of getting these pulled in
} On Wed, Oct 06, 2010 at 05:04:06PM +0200, Martin Husemann wrote:
} > I'm testing the patch in -current with these hardware:
} > 
} > bge0 at pci2 dev 0 function 0: Broadcom BCM57780 Fast Ethernet
} > bge0: interrupting at ioapic0 pin 16
} > adjust device control 0x192000 -> 0x195000
} > bge0: ASIC BCM57780 A1 (0x57780001), Ethernet address 00:26:2d:90:46:d1
} > bge0: setting short Tx thresholds
} > ukphy0 at bge0 phy 1: OUI 0x001be9, model 0x0019, rev. 1
} > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
} 
} [...]
} 
} > I found no problems so far.
} 
} Bah, after quite some testing I now got in situations where heavy load
} NFS traffic made the system hang - dropping all the offloading options
} made it work again. This is on a notebook, and I don't regularily use
} the server where it happens - no idea why the same traffic to a similar
} machine works fine.
} 
} Martin
>-- End of excerpt from Martin Husemann