From: "mirabilos" <eccesys@topmail.de>
To: "Linux-Kernel ML" <linux-kernel@vger.kernel.org>,
"Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>
Subject: Re: hard crashes 2.4.0/1 with NE2K stuff
Date: Fri, 2 Feb 2001 13:59:13 -0000 [thread overview]
Message-ID: <024a01c08d20$5db6b9e0$0100a8c0@homeip.net> (raw)
In-Reply-To: <20010201231652.A2684@grobbebol.xs4all.nl>
----- Original Message -----
From: "Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, February 01, 2001 11:16 PM
Subject: hard crashes 2.4.0/1 with NE2K stuff
> 2.4.1. rebuilt here and with a floodping towards my machine causes a
> hard crash where nothing works anymore.
>
> just before it happens :
>
> Feb 1 13:07:24 grobbebol kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Feb 1 13:07:24 grobbebol kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=21.
> Feb 1 13:07:36 grobbebol kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Feb 1 13:07:36 grobbebol kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0xb7, t=38.
> Feb 1 13:07:41 grobbebol kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Feb 1 13:07:41 grobbebol kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0xb7, t=38.
> Feb 1 13:07:43 grobbebol kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Feb 1 13:07:43 grobbebol kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x97, t=118.
> Feb 1 13:07:45 grobbebol kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Feb 1 13:07:45 grobbebol kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x97, t=118.
> Feb 1 13:07:46 grobbebol kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Feb 1 13:07:46 grobbebol kernel: eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x97, t=38.
>
>
> note that it doesn't happen when 2.2.19pre* is used. Still some work
> there to do.
>
> the used board BP6 (abit), apics enabled. non-overclocked. card is a
>
> 00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8029(AS)
>
> IRQ:
>
> 19: 6851 7642 IO-APIC-level eth0
>
> I assume Franks suggestions didn't get into the kernel ?
I have UP P133/56MB, 2.4.1-vanilla, some config changes.
NE2K works fine for me though software watchdog enabled.
I didn't strain test it yet, but will do l8er.
-mirabilos
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12+(proprietary extensions) # Updated:20010129 nick=mirabilos
GO/S d@ s--: a--- C++ UL++++ P--- L++$(-^lang) E----(joe) W+(++) loc=.de
N? o K? w-(+$) O+>+++ M-- V- PS+++@ PE(--) Y+ PGP t+ 5? X+ R+ !tv(silly)
b++++* DI- D+ G(>++) e(^age) h! r(-) y--(!y+) /* lang=NASM;GW-BASIC;C */
------END GEEK CODE BLOCK------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-02 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 23:16 Roeland Th. Jansen
2001-02-02 0:13 ` Alan Cox
2001-02-02 9:26 ` Roeland Th. Jansen
2001-02-02 10:58 ` Roeland Th. Jansen
2001-02-02 13:59 ` mirabilos [this message]
2001-02-02 13:52 Frank de Lange
2001-02-02 14:55 ` Roeland Th. Jansen
2001-02-02 20:42 ` Maciej W. Rozycki
2001-02-03 11:36 ` Roeland Th. Jansen
2001-02-05 10:19 ` Maciej W. Rozycki
2001-02-05 18:26 ` Roeland Th. Jansen
2001-02-05 19:41 ` Roeland Th. Jansen
2001-02-05 19:49 ` Frank de Lange
2001-02-05 20:16 ` Roeland Th. Jansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='024a01c08d20$5db6b9e0$0100a8c0@homeip.net' \
--to=eccesys@topmail.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roel@grobbebol.xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®