All of lore.kernel.org
 help / color / mirror / Atom feed
From: LaMont Jones <lamont@security.hp.com>
To: Paul Bame <bame@debian.fc.hp.com>
Cc: "John David Anglin" <dave@hiauly1.hia.nrc.ca>,
	parisc-linux@thepuffingroup.com, lamont@security.hp.com
Subject: Re: [parisc-linux] a pretty big change
Date: Wed, 08 Dec 1999 18:08:20 -0700	[thread overview]
Message-ID: <19991209010821.87E9318708@security.hp.com> (raw)
In-Reply-To: Your message of "Tue, 07 Dec 1999 09:53:02 MST." <199912071653.JAA18644@debian.fc.hp.com>

> That happens pretty frequently to me but I've not tracked down why
> it happens.  Did you try holding the TOC button in for several seconds?
> On some workstations I've been told that generates a hard reset.

TOC results in (providing that the checksum passes) transfer of control
to a routine pointed at from page 0.  If something is trashing that, and
the checksum'ed length is set to 0, then you'll branch off into the ozone.

If the checksum fails, then you get the PDC default of rebooting.

Don't know if that's your problem, but it's probably worth checking into
whether something is trashing physical address 8 (TOC vector - 0xc is the
length of the checksum.)

lamont

  reply	other threads:[~1999-12-09  1:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-04  0:20 [parisc-linux] a pretty big change Paul Bame
1999-12-04  1:28 ` Paul Bame
1999-12-07  4:50   ` John David Anglin
1999-12-07 16:53     ` Paul Bame
1999-12-09  1:08       ` LaMont Jones [this message]
1999-12-12 17:54         ` John David Anglin
1999-12-04  1:31 ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
1999-12-08 13:27 Ulrich Strelow
1999-12-08 15:54 ` Paul Bame
1999-12-09 12:24 Ulrich Strelow
1999-12-09 21:21 ` John David Anglin
     [not found] <19991209122240.1018.qmail@web506.mail.yahoo.com>
1999-12-10 17:15 ` Paul Bame
1999-12-10 17:49   ` John David Anglin

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=19991209010821.87E9318708@security.hp.com \
    --to=lamont@security.hp.com \
    --cc=bame@debian.fc.hp.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@thepuffingroup.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.