public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Probable seamless bug: can't pop es
Date: Fri, 12 Oct 2001 01:11:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805338@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805337@msgid-missing>

>>>>> On Thu, 11 Oct 2001 17:19:32 -0700, "Robboy, David G" <david.g.robboy@intel.com> said:

  David.R> The following simple program runs on a P4 linux system, but
  David.R> gets a SIGSEGV on an Itanium.  Most likely a seamless bug
  David.R> rather than a hardware bug.  Even though we don't use
  David.R> segment registers in Linux, it is legal to push and pop
  David.R> them, isn't it?

Actually, even segmentation is supported (via modify_ldt()), so the
program should work.  GDB says it dies on the "popl" instruction.  The
address that triggering the fault is 0x4c.  I don't see where this is
coming from.  My suspicion is that the segv happens when the CPU
attempts to load the segment descriptor from the GDT, but if that's
the case, the address should be somewhere in the 0xc0000000 range.
Another possibility is that the GDTD is not set up properly, but I
don't see anything obvious that's wrong there.

Perhaps someone more familiar with x86 could take a look?

	--david


  reply	other threads:[~2001-10-12  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12  0:19 [Linux-ia64] Probable seamless bug: can't pop es Robboy, David G
2001-10-12  1:11 ` David Mosberger [this message]
2001-10-14 18:35 ` n0ano
2001-10-15 17:11 ` David Mosberger

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=marc-linux-ia64-105590698805338@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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