From: Chris Jantzen <chris-parisc@maybe.net>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] 3c597 Questions
Date: Sat, 12 Oct 2002 06:43:43 -0700 [thread overview]
Message-ID: <20021012134343.GM841@maybe.net> (raw)
I have a couple 3com 3c597's (EISA) in a C180 and even touching the
3c59x driver tends to cause bad things to happen. Has anyone ever
touched these drivers? Where would I start doing serious debugging? I
can't even tell you if it's doing an HPMC or not, much less what the
oops is actually saying. FAQ's on kernel debugging? Thanks!
--
chris jantzen kb7rnl =-> __O
Insert witty comment here. _`\<,_
http://www.maybe.net/ (*)/ (*)
reply other threads:[~2002-10-12 13:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021012134343.GM841@maybe.net \
--to=chris-parisc@maybe.net \
--cc=parisc-linux@lists.parisc-linux.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.