We're seeing this identical timeout starting with 2.6.21, any time we try and
push a significant amount of traffic through the nforce ethernet. We've rolled
back to 2.6.20.18 and don't see any problems. It seems that this bug got
introduced along with all the forcedeth fixes and optimizations in
On Fri, Aug 24, 2007 at 07:18:55AM -0500, Mr. Berkley Shands wrote:
> No joy.
>
> I did a ping during the "make -j4"... it starts dropping packets, and
> gets to a 2-in-a-row, then hangs.
> This time there was no error output in /var/log/messages.
>
> Usually there is something..
Ok, but please
On Fri, Aug 24, 2007 at 06:26:59AM -0500, Mr. Berkley Shands wrote:
> 2.6.20 didn't show this issue. 2.6.21 did, and all 2.6.22 up to
> 2.6.22.5 all show it.
> I'll test the patch in an hour or so.
I don't think it's much related then (though I don't know its real implications)
Willy
-
To unsu
On Thu, Aug 23, 2007 at 06:48:23PM -0500, Mr. Berkley Shands wrote:
> 100% reproducible hang on xmit timeout.
> Just do a "make -j4 modules" on an nfs mounted kernel source.
Most likely you also had the problem with 2.6.22.2 (maybe you have not
tested this one, though). There were bug fixes for fo
100% reproducible hang on xmit timeout.
Just do a "make -j4 modules" on an nfs mounted kernel source.
attached is the messages log
berkley
--
// E. F. Berkley Shands, MSc//
** Exegy Inc.**
349 Marshall Road, Suite 100
St. Louis , MO 63119
Direct: (314) 218-3600 X450
Cell: (314) 303-2546
5 matches
Mail list logo
