On Fri, Oct 13, 2006 at 12:56:53PM +0100, David Johnson wrote:
> On Friday 13 October 2006 11:58, Jarek Poplawski wrote:
> >
> > PS: I hope you tested it also under internal stress (heavy
> > copying plus computing).
>
> Yes, I did. No individual factor triggers the bug (high CPU load, lots of disk
> activity, high network load, etc.) nor does any other combination of factors
> other than what I mentioned before (high network load, some disk activity,
> some CPU load).
>
> Both scp and rsync trigger it reliably, but FTP does not trigger it at all. So
> CPU load (which scp and rsync generates but FTP does not) must be a key part
> of the equation...
Probably - but only with networking. So I'd try with this debugging
like in my first reply plus maybe 2.6.19-rc1 (e1000 - btw. I hope
this other tested card was different model - and locking improved)
and resend conclusions to [email protected].
Cheers,
Jarek P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
