From: sah@borf.com
To: 9fans@cse.psu.edu
Subject: [9fans] oddity
Date: Wed, 19 Jul 2000 10:33:32 -0400 [thread overview]
Message-ID: <Pine.LNX.4.10.10007191028580.32506-100000@linux.borf.com> (raw)
Hello,
I've my fileserver and auth/cpu server up now, and am attempting to boot
terminals. The terminal sets to boot from ether0, finds its kernel from
the network, and starts to boot. It then hangs.
So I placed a multitude of print statements in, tracking down the hanging
portion of the code. I know this sounds crazy, but it hangs randomly in
different parts of the reset ethernet card code. Has anyone previously
encountered this and can you give me a trail to head down?
Sam
--------------------------------------------------------------
Sam Hopkins
sah@borf.com
"... let us tame the savageness of man, and make
gentle the life of this world."
next reply other threads:[~2000-07-19 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 14:33 sah [this message]
2000-07-20 2:36 ` Eric Dorman
2000-07-20 11:28 ` sah
2000-07-19 15:54 Russ Cox
2000-07-19 18:15 ` Peter LeBlond
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=Pine.LNX.4.10.10007191028580.32506-100000@linux.borf.com \
--to=sah@borf.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).