[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [cobalt-users] Raq3i: onboard-NIC dies under heavy load
- Subject: AW: [cobalt-users] Raq3i: onboard-NIC dies under heavy load
- From: "Gunther Stammwitz" <gstammw@xxxxxxx>
- Date: Mon Dec 23 04:52:03 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Hello Gerald,
First of all: thanks a lot for your help.
I'm using a 2.4.18-kernel, so it should be patched:
uname -a
Linux myhost 2.4.18 #14 Sat Oct 19 20:02:08 CEST 2002 i586 unknown
I've been using the standard 2.4.18-kernel-source. I've configured it this
way:
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set
--> so it is disabled. Is that okay or do I still need those patches you
were talking about ?
Bye,
Gunther
-----Ursprüngliche Nachricht-----
Von: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] Im Auftrag von Gerald Waugh
Gesendet: Montag, 23. Dezember 2002 13:22
An: cobalt-users@xxxxxxxxxxxxxxx
Betreff: Re: [cobalt-users] Raq3i: onboard-NIC dies under heavy load
On Mon, 23 Dec 2002, Gunther Stammwitz wrote:
>
> I'm using my cobalt RaQ 3i as a firewall. It is equipped with two
> onboard intel-nics and one additional tulip-based nic in the pci slot.
> The bios has been flashed and the box is running debian with a
> 2.4.x-kernel.
>
> The problem is, that the box is carrying about 30 to 40 megabits per
> seconds
> - which means routing from one nic to the other. After running fine for a
> period that changes between just 3 hours or even 3 days the box looses the
> network-connection on one the first onboard nic (eth0). The second
> onboard-nic has died since such an event. DMESG logs some kind of
> netdev-watch-message: NETDEV WATCHDOG: eth2: transmit timed out NETDEV
> WATCHDOG: eth2: transmit timed out NETDEV WATCHDOG: eth2: transmit timed
out
> NETDEV WATCHDOG: eth2: transmit timed out NETDEV WATCHDOG: eth2: transmit
> timed out
>
> The link on the nic is still up, but I cannot transfer any data. After
> rebooting everything is fine again. Any ideas ?? Maybe - the nics are
> getting too hot ???
>
A few things I found
There is/was a kernel problem, I believe in 2.4.16 but was fixed in 2.4.17
Don't configure your kernel to use IO-APIC Use 2.4.x-ac kernels, which have
a workaround.
Gerald
--
http://frontstreetnetworks.com | http://raqware.com
Front Street Networks LLC | Phone: +1 203-785-0699
229 Front Street, Ste. C, New Haven, CT. 06513-3203
_____________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users