ben soo wrote:
i spoke too soon. The Gbit interface still dies. Lasted around 19hrs.
or so. i can't tell if there are hardware issues: yesterday a Gbit NIC
on the firewall died. Different chip (Realtek), different driver,
different machine, same segment. Segment is a mix of 100Mbit and 1Gb
On Sat, 22 Sep 2007 21:56:04 -0400
ben soo <[EMAIL PROTECTED]> wrote:
> i spoke too soon. The Gbit interface still dies. Lasted around
> 19hrs. or so. i can't tell if there are hardware issues: yesterday
> a Gbit NIC on the firewall died. Different chip (Realtek),
> different driver, differ
i spoke too soon. The Gbit interface still dies. Lasted around
19hrs. or so. i can't tell if there are hardware issues: yesterday
a Gbit NIC on the firewall died. Different chip (Realtek),
different driver, different machine, same segment. Segment is a
mix of 100Mbit and 1Gbit machines.
ben soo wrote:
[...]
This last might be an artifact caused by the firewall, i dunno.
[...]
Bill Davidsen <[EMAIL PROTECTED]> wrote:
Yes, I have found that I get far less problem in this area leaving the
MTU at 1500, then putting a larger MTU (usually 9000) into the routing
table for segment
On Tue, 18 Sep 2007 10:28:43 -0400
Bill Davidsen <[EMAIL PROTECTED]> wrote:
> ben soo wrote:
> > i'm experiencing this problem myself. i have 2 servers, one using
> > X86_64 kernel version 2.6.23-rc5 on a 100Mbit network and one with i386
> > kernel version 2.6.23-rc6 on a 1Gbit network.
> >
>
ben soo wrote:
i'm experiencing this problem myself. i have 2 servers, one using
X86_64 kernel version 2.6.23-rc5 on a 100Mbit network and one with i386
kernel version 2.6.23-rc6 on a 1Gbit network.
They both have this issue with the sky2 network device driver whereby
the device would stop w
i'm experiencing this problem myself. i have 2 servers, one using
X86_64 kernel version 2.6.23-rc5 on a 100Mbit network and one with
i386 kernel version 2.6.23-rc6 on a 1Gbit network.
They both have this issue with the sky2 network device driver
whereby the device would stop working and need
[1.] One line summary of the problem:
hw csum failure appears in syslog
[2.] Full description of the problem/report:
hw csum failure appears in syslog and sometimes, under heavy network utilization, with NFS-Daemon the Network Device
totally fails. Then no Network Access is possible. Reboo
8 matches
Mail list logo