From: Nathan Walp <faceprint@faceprint.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.1-ac13 tulip problems
Date: Wed, 14 Feb 2001 17:07:24 -0500 [thread overview]
Message-ID: <3A8B019C.4F0C76DB@faceprint.com> (raw)
I just booted to 2.4.1-ac13, and was fine for a couple minutes. Then
all network connectivity went away, and I had this sitting in syslog:
Feb 14 16:45:48 patience kernel: LDT allocated for cloned task!
Feb 14 16:47:19 patience kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Feb 14 16:47:51 patience last message repeated 4 times
Feb 14 16:48:55 patience last message repeated 8 times
Feb 14 16:49:59 patience last message repeated 8 times
Feb 14 16:51:03 patience last message repeated 8 times
Feb 14 16:51:51 patience last message repeated 6 times
<snip>
Feb 14 16:51:59 patience kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Feb 14 16:52:31 patience last message repeated 4 times
Feb 14 16:53:35 patience last message repeated 8 times
Feb 14 16:54:39 patience last message repeated 8 times
Feb 14 16:54:47 patience kernel: NETDEV WATCHDOG: eth0: transmit timed
out
Feb 14 16:54:49 patience kernel: inet6_ifa_finish_destroy
Feb 14 16:54:49 patience kernel: inet6_ifa_finish_destroy
Feb 14 16:54:57 patience kernel: eth0: Setting half-duplex based on
MII#1 link partner capability of 0021.
Feb 14 16:55:15 patience kernel: eth0: no IPv6 routers present
Feb 14 16:55:15 patience kernel: eth0: no IPv6 routers present
Hence, I'm back to 2.4.1-ac12, and sending this in. No other noticible
problems in my short-lived uptime ;-)
Nathan
next reply other threads:[~2001-02-14 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 22:07 Nathan Walp [this message]
2001-02-14 22:11 ` 2.4.1-ac13 tulip problems Alan Cox
2001-02-14 22:15 ` Nathan Walp
2001-02-14 22:17 ` Manfred Spraul
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=3A8B019C.4F0C76DB@faceprint.com \
--to=faceprint@faceprint.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.