From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] waserror()/nexterror()
Date: Fri, 16 Jan 2004 15:42:51 -0500 [thread overview]
Message-ID: <dfe97dc6ab781f7dc67a2000f65ce3b0@plan9.bell-labs.com> (raw)
In-Reply-To: <20040116204209.V25947@cackle.proxima.alt.za>
On Fri Jan 16 13:43:40 EST 2004, lucio@proxima.alt.za wrote:
> ...
>
> I figure that the SiS is not a properly grown up P5. Cpuidentify(),
> however, seems to think it is, so when it sets "tsc", it blows the
> chip out the water. I added a
> ...
what would be useful is the output of /bin/pci.
next prev parent reply other threads:[~2004-01-16 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 9:17 Lucio De Re
2004-01-16 9:20 ` Fco.J.Ballesteros
2004-01-16 9:38 ` Lucio De Re
2004-01-16 10:00 ` Lucio De Re
2004-01-16 11:49 ` Charles Forsyth
2004-01-16 15:37 ` jmk
2004-01-16 18:42 ` Lucio De Re
2004-01-16 20:42 ` jmk [this message]
2004-01-17 6:38 ` Lucio De Re
2004-01-16 15:42 ` ron minnich
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=dfe97dc6ab781f7dc67a2000f65ce3b0@plan9.bell-labs.com \
--to=jmk@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).