Hi,

I'm using Debian 4.0r0 kernel 2.6.18.
Whenever gigabit (marvell) is stressed a lot ( with netcat or ftp), I get about 30Mb/s, which is nice.

Unfortunately, the system locks or even reboots after a few minutes.
I experienced the same prob on Suse10.2 and later, but not on Suse10.1.
Is there hope on later kernels or is the bug still present ?

( Note: I'm sure, it's no hardware problem, as the machine performs perfect over hours with suse10.1.. and all of my 3 Peg2's behave the same.)

i had quite the same issue having 1,5 Gb of Ram in the Pegasos2. Removing 512Mb fixed it.
But i suppose you're on a different story.

It's a kernel bug. I experienced the crash on Suse10.2, but not on Suse 10.1. (But also on Debian, Ubuntu and some others.)

As Suse 10.3 with it's very new kernel seems to work perfectly with gigabit again, I'll try 2.6.22 on debian to try whether it's fixed there, too.

I had the same on my Peg2 with 1GB RAM, running Debian Etch. I upgraded to 2.6.21.4, and that fixed it. But 2.6.18 kernel was highly unstable for me, even without the use of the GBit eth. I changed, and all problems gone:
Previous record uptime with 2.6.18 (stock Debian 4.0r0 kernel) was 4 days:
... and usually it crashed within one day:
Sarge was totally stable on the same machine. So it seems like the some kernel versions (most probably versions between 2.6.15 and 2.6.20?) has serious stability issues on a Pegasos 2...