From: Stephen Thomas <stephen.thomas@insignia.com>
To: linux-kernel@vger.kernel.org
Subject: Tulip in 2.4.1-ac14 still poorly
Date: Fri, 16 Feb 2001 11:18:42 +0000 [thread overview]
Message-ID: <3A8D0C92.7060AABE@insignia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 196 bytes --]
On trying 2.4.1-ac13 I hit the tulip driver problems reported elsewhere,
and ac14 does not seem to fix the problem on my machine. Attached is an
extract from my /var/log/messages.
Stephen Thomas
[-- Attachment #2: messages-2.4.1-ac14 --]
[-- Type: text/plain, Size: 2281 bytes --]
Feb 15 16:07:32 triumph kernel: Linux version 2.4.1-ac14 (root@triumph.isltd.insignia.com) (gcc version 2.95.2 19991024 (release)) #1 Thu Feb 15 15:53:08 GMT 2001
[ ... ]
Feb 15 16:07:33 triumph kernel: Detected 400.915 MHz processor.
[ ... ]
Feb 15 16:07:33 triumph kernel: Memory: 126652k/131008k available (1009k kernel code, 3968k reserved, 372k data, 188k init, 0k highmem)
[ ... ]
Feb 15 16:07:35 triumph kernel: CPU: Intel Pentium II (Deschutes) stepping 01
[ ... ]
Feb 15 16:07:39 triumph kernel: Linux Tulip driver version 0.9.13b (January 24, 2001)
Feb 15 16:07:39 triumph kernel: PCI: Found IRQ 10 for device 00:10.0
Feb 15 16:07:39 triumph kernel: eth0: Lite-On 82c168 PNIC rev 32 at 0xe400, 00:C0:F0:2C:2B:3A, IRQ 10.
Feb 15 16:07:39 triumph kernel: eth0: MII transceiver #1 config 3100 status 7829 advertising 01e1.
[ ... ]
Feb 15 16:07:54 triumph amd[601]: vim:/ mounted fstype host on /.automount/vim/root
Feb 15 16:08:03 triumph ypbind[373]: unknown: RPC: Timed out
Feb 15 16:08:06 triumph kernel: nfs: server vim not responding, still trying
Feb 15 16:08:06 triumph last message repeated 2 times
Feb 15 16:08:07 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:08:14 triumph PAM-securetty[741]: Couldn't open /etc/securetty
Feb 15 16:08:15 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:08:19 triumph amd[601]: file server vim type nfs is down
Feb 15 16:08:23 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:08:55 triumph last message repeated 4 times
Feb 15 16:08:57 triumph ypbind[373]: broadcast: RPC: Timed out.
Feb 15 16:09:03 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:09:35 triumph last message repeated 4 times
Feb 15 16:09:51 triumph last message repeated 2 times
Feb 15 16:09:55 triumph kernel: nfs: task 99 can't get a request slot
Feb 15 16:09:59 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:10:01 triumph ypbind[373]: broadcast: RPC: Timed out.
Feb 15 16:10:07 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:10:11 triumph PAM-securetty[772]: Couldn't open /etc/securetty
Feb 15 16:10:15 triumph kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb 15 16:10:47 triumph last message repeated 4 times
next reply other threads:[~2001-02-16 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 11:18 Stephen Thomas [this message]
2001-02-16 11:47 ` Tulip in 2.4.1-ac14 still poorly Manfred Spraul
2001-02-16 12:05 ` Stephen Thomas
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=3A8D0C92.7060AABE@insignia.com \
--to=stephen.thomas@insignia.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.