9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] waserror()/nexterror()
Date: Fri, 16 Jan 2004 10:37:06 -0500	[thread overview]
Message-ID: <d749a6d6cb37a9c5aa90b5a8bdb62311@plan9.bell-labs.com> (raw)
In-Reply-To: <887916726fef37e3c6950c109038f988@terzarima.net>

On Fri Jan 16 06:50:39 EST 2004, forsyth@terzarima.net wrote:
> >>whereas something very early in the 4ed kernel startup (before any
> >>printed announcements) causes the kernel to reset the host.
>
> i noticed that recently on a 486-class device that did run a few months ago.
> i'd wondered if it might have been the changes to devarch.c/l.s but
> it wasn't urgent enough for me to debug it yet, nor was
> i sure until i saw your remark that it wasn't more likely
> some blunder of my own (eg, inconsistent mk)

For some time Plan 9 on sources had the 'coherence' variable in pc/devarch.c
initialised to to something that wouldn't work on an x86 that didn't have the
CPUID instruction, e.g. the 386 and most 486. I attempted to fix it a few weeks
ago, if your kernel has the current devarch.c, fns.h and l.s and still doesn't
work, let me know.

--jim


  reply	other threads:[~2004-01-16 15:37 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 [this message]
2004-01-16 18:42         ` Lucio De Re
2004-01-16 20:42           ` jmk
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=d749a6d6cb37a9c5aa90b5a8bdb62311@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).