Matt Mackall wrote:
Ok, reproduceable without ssh makes narrowing this down much easier.
Are you seeing errors on the interface? No would indicate problems
post CRC checking on the receive side. Do errors happen in both
directions? If not, it may be CPU speed-related or specific to a given
NIC -
Matt Mackall wrote:
Ok, reproduceable without ssh makes narrowing this down much easier.
Are you seeing errors on the interface? No would indicate problems
post CRC checking on the receive side. Do errors happen in both
directions? If not, it may be CPU speed-related or specific to a given
NIC -
Hi,
On Thu, Feb 03, 2005 at 11:16:37PM -0500, Ethan Weinstein wrote:
(...)
> Excellent tip, thanks. I was able to reprodce the problem several times
> using this technique with nc, however the problem was intermittent (as
> nasty problems like this often are). I used a 1.3G gzipped tarball
On Thu, Feb 03, 2005 at 11:16:37PM -0500, Ethan Weinstein wrote:
> Matt Mackall wrote:
> >On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
> ...
> >>Finally, I used a crossover cable between the two boxes, which resulted
> >>in the same error from sshd again.
> >
> >
> >Well ssh
Matt Mackall wrote:
On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
...
Finally, I used a crossover cable between the two boxes, which resulted
in the same error from sshd again.
Well ssh isn't an especially good test as it's hard to debug.
Try transferring large compressed
Matt Mackall wrote:
On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
...
Finally, I used a crossover cable between the two boxes, which resulted
in the same error from sshd again.
Well ssh isn't an especially good test as it's hard to debug.
Try transferring large compressed
On Thu, Feb 03, 2005 at 11:16:37PM -0500, Ethan Weinstein wrote:
Matt Mackall wrote:
On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
...
Finally, I used a crossover cable between the two boxes, which resulted
in the same error from sshd again.
Well ssh isn't an
Hi,
On Thu, Feb 03, 2005 at 11:16:37PM -0500, Ethan Weinstein wrote:
(...)
Excellent tip, thanks. I was able to reprodce the problem several times
using this technique with nc, however the problem was intermittent (as
nasty problems like this often are). I used a 1.3G gzipped tarball and
On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
> Hey all,
>
> I've been having quite a time with the e1000 driver running at gigabit
> speeds. Running it at 100Fdx has never been a problem, which I've done
> done for a long time. Last week I picked up a gigabit switch, and
Hey all,
I've been having quite a time with the e1000 driver running at gigabit
speeds. Running it at 100Fdx has never been a problem, which I've done
done for a long time. Last week I picked up a gigabit switch, and that's
when the trouble began. I find that transferring large amounts of
Hey all,
I've been having quite a time with the e1000 driver running at gigabit
speeds. Running it at 100Fdx has never been a problem, which I've done
done for a long time. Last week I picked up a gigabit switch, and that's
when the trouble began. I find that transferring large amounts of
On Wed, Feb 02, 2005 at 10:44:14PM -0500, Ethan Weinstein wrote:
Hey all,
I've been having quite a time with the e1000 driver running at gigabit
speeds. Running it at 100Fdx has never been a problem, which I've done
done for a long time. Last week I picked up a gigabit switch, and that's
12 matches
Mail list logo
