Re: Transmit timeout with 3c395, 2.4.19, 2.4.22
From: Stian Jordet (liste_at_jordet.nu)
Date: 10/30/03
- Previous message: Bartlomiej Zolnierkiewicz: "Re: Processes receive SIGSEGV if TCQ is enabled"
- In reply to: Andrew Morton: "Re: Transmit timeout with 3c395, 2.4.19, 2.4.22"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: linux-kernel@vger.kernel.org Date: Thu, 30 Oct 2003 18:50:22 +0100
man, 27.10.2003 kl. 20.18 skrev Andrew Morton:
> Norbert Preining <preining@logic.at> wrote:
> >
> > Hi Andrew, hi list!
> >
> > Suddenly, after 160 days of running, our bridged firewall started to
> > spit out this:
> > NETDEV WATCHDOG: eth1: transmit timed out
My gateway started to give me this errors on eth0 some days ago. Eth0 is
the internal network-card, which is connected to just one pc through a
crossed tp-cable. When I run a certain app on my pc (xMule), the gateway
alway starts spitting those messages.
Could have been hardware, but only happens when xmule is active on my
computer. Wasn't like this earlier.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Bartlomiej Zolnierkiewicz: "Re: Processes receive SIGSEGV if TCQ is enabled"
- In reply to: Andrew Morton: "Re: Transmit timeout with 3c395, 2.4.19, 2.4.22"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|