From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] exception / interrupt 14 again
Date: Tue, 14 May 2002 11:37:30 -0400 [thread overview]
Message-ID: <0c3670567a15812a9148a1081deb41e3@plan9.bell-labs.com> (raw)
> 2 thinkpads (760L and 600E) and a Compaq Armada 7770DMT
i'm curious to see what their apm lines say
at boot time, just to see what interesting bits
of code were being incremented on those machines.
the new disk should fix them. let me know if it doesn't.
russ
next reply other threads:[~2002-05-14 15:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 15:37 Russ Cox [this message]
2002-05-15 9:20 ` Don
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 9:38 rsc
2002-05-16 9:05 ` Don
2002-05-10 21:14 Woodruff, Richard
2002-05-10 19:33 Russ Cox
2002-05-10 16:56 Woodruff, Richard
2002-05-10 11:47 Russ Cox
2002-05-14 13:32 ` Don
2002-05-09 18:44 Russ Cox
2002-05-10 8:44 ` Don
2002-05-07 20:11 Woodruff, Richard
2002-05-09 8:56 ` Joel Salomon
2002-05-07 0:51 Artem Letko
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=0c3670567a15812a9148a1081deb41e3@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).