9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: Panic: Lock Loop On Inserting Disk2.vd.
Date: Wed, 13 Sep 1995 05:47:35 -0400	[thread overview]
Message-ID: <19950913094735.5xYPeZ3IPEuDQh_4u2ai9BkyhTJPrLEkqS8ieeJtum8@z> (raw)

i've seen this on two machines that had incorrect BIOS advanced/chipset
parameters (including the one i'm using now).  the BIOS default parameters
were definitely wrong for my configuration -- they worked, but
assumed rather slow memory -- but my first attempts were too optimistic

the system got all the way through termrc but blew up with a lock loop
when starting all my windows in 8½.  i suspect that the lock word flushed
from the cache didn't make it to memory because the memory write time allowance
was too low.  i added another wait state and it has been fine since.
the little handbooks that come with
the motherboard rarely give enough information to allow you to work out the
correct values to use.
the m/b i'm using now comes with better documentation than most, but
it still wasn't enough.
proper computers are designed to support a particular combination of things,
with fairly tight limits; the average PC motherboard and chipset must accept
almost anything, hence all the options.

i don't suppose there is a document on the net somewhere about these
settings, written by someone who knows?






             reply	other threads:[~1995-09-13  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-09-13  9:47 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-09-14 17:36 ralphc
1995-09-13  3:15 jmk
1995-09-12 10:33 ralphc

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=19950913094735.5xYPeZ3IPEuDQh_4u2ai9BkyhTJPrLEkqS8ieeJtum8@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /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).