linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: icedank@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: Stored data missed in setup.S
Date: Wed, 23 Apr 2003 11:11:58 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304231107530.23670@chaos> (raw)
In-Reply-To: <20030423075158.510e25d2.rddunlap@osdl.org>

On Wed, 23 Apr 2003, Randy.Dunlap wrote:

> On Wed, 23 Apr 2003 10:36:55 -0400 (EDT) "Richard B. Johnson" <root@chaos.analogic.com> wrote:
>
> | On Wed, 23 Apr 2003, Andrew Kirilenko wrote:
> |
> | [SNIPPED...]
> |
> | > OK. And now code looks like:
> | > -->
> | > start_of_setup: # line 160
> | > 	# bla bla bla - some checking code
> | >         movb    $1, %al
> | >         movb    %al, (0x100)
> | > ....
> | > ....
> | > 	cmpb    $1, (0x100)
> | > 	je bail820 # and it DON'T jump here
> | > <--
> | >
> |
> | > I'm sure, I'm doing something wrong. But what???
> |
> | The only possibiity is that the code you just showed is not
> | being executed. Absolute location 0x100 is not being overwritten
> | by some timer-tick (normally) so whatever you write there should
> | remain. You just put a byte of 1 in that location and then
> | you compared against a byte of 1. If the CPU was broken, you
> | wouldn't have even loaded your code.
>
> Could possibly be that DS (seg register) is altered between
> the store and the comparison...

I can only assume that the code presented is the only code that
was executed. You are correct that DS may have never even been
set. The data segment may be in some non-writable space, which
is hard to find now-days with most evenything being shadowed
and left writable. Many modern chip-sets can't turn off write,
maybe it was too expensive from a performance standpoint.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


      reply	other threads:[~2003-04-23 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 13:17 Stored data missed in setup.S Andrew Kirilenko
2003-04-23 13:33 ` Richard B. Johnson
2003-04-23 13:39   ` Andrew Kirilenko
2003-04-23 14:36     ` Richard B. Johnson
2003-04-23 14:50       ` Andrew Kirilenko
2003-04-23 15:06         ` Richard B. Johnson
2003-04-23 14:51       ` Randy.Dunlap
2003-04-23 15:11         ` Richard B. Johnson [this message]

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=Pine.LNX.4.53.0304231107530.23670@chaos \
    --to=root@chaos.analogic.com \
    --cc=icedank@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /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).