From: Manfred Spraul <manfred@colorfullife.com>
To: whitney@math.berkeley.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to debug a 2.4.4 tulip problem?
Date: Sat, 05 May 2001 03:07:18 +0200 [thread overview]
Message-ID: <3AF35246.420B2E1A@colorfullife.com> (raw)
>
> What information should I gather when the card is wedged to aid in
> debugging? Is 'lspci -xxx' enough? Any suggestions would be welcome.
>
tulip-diag from www.scyld.com.
Do you know if transmit or receive is slow? tcpdump on both ends of the
ping might help.
next reply other threads:[~2001-05-05 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 1:07 Manfred Spraul [this message]
2001-05-05 1:10 ` Wayne Whitney
2001-05-06 1:03 ` Wayne Whitney
-- strict thread matches above, loose matches on Subject: below --
2001-05-05 0:39 Wayne Whitney
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=3AF35246.420B2E1A@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=whitney@math.berkeley.edu \
/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®